Discover and read the best of Twitter Threads about #isq
Most recents (2)
some dev work (e.g. enhancements, modernization) is
"tweak/refactor + copy-paste + tweak/refactor"
w/ varying amounts of "tweak" depending on the work
i.e. there's this thing that "works" already; they want a slight enhancement, or new look n feel
like a transplant
1/4
"tweak/refactor + copy-paste + tweak/refactor"
w/ varying amounts of "tweak" depending on the work
i.e. there's this thing that "works" already; they want a slight enhancement, or new look n feel
like a transplant
1/4
most attention/energy expectation is paid to the level of effort it takes just to do the "copy-paste" part
and dev teams have a hard time justifying that it takes more than just ctrl+c, ctrl+v
we all want to believe that the work is just two key strokes and a mouse drag
2/4
and dev teams have a hard time justifying that it takes more than just ctrl+c, ctrl+v
we all want to believe that the work is just two key strokes and a mouse drag
2/4
but in reality, that's not even really a third of the work involved
most of the effort is in the tweaks and refactorings
be aware (and beware) of these steps
mention each step, communicate these to the stakeholders
3/4
most of the effort is in the tweaks and refactorings
be aware (and beware) of these steps
mention each step, communicate these to the stakeholders
3/4
on an agile team, whenever someone uses the word "story" and "requirement" to mean the same thing, an angel loses her wings
how do you point out the benefits of using one over the other?
"story" frames with problem, with the person at the center
"requirement" focus on the product, teh soul-less tech
"story" frames with problem, with the person at the center
"requirement" focus on the product, teh soul-less tech
it's better to talk about the user, the user scenario, the actual problem, (the domain), than it is to base your work on clever algorithms and hyped up, buzzwordy shiny tech
