In examining my process, I spend most of my time futzing with stuff. That's the best way to put it.
Basically a task is somewhat done, but the last mile of tests, edge cases, light refactoring — once it essentially works already takes up much more time than actually getting it to essentially work in the first place.
This may be a bad answer. Looking forward to reading what direction other folks take this question in.
This is a great answer IMO. And it really paints the picture of what kind of dev you are: mature enough to know that "it works" doesn't necessarily cut it, experienced enough to visualize what else remains to be done, persistent enough to get it across the finish line. I think those are essential traits in a senior dev.
In examining my process, I spend most of my time futzing with stuff. That's the best way to put it.
Basically a task is somewhat done, but the last mile of tests, edge cases, light refactoring — once it essentially works already takes up much more time than actually getting it to essentially work in the first place.
This may be a bad answer. Looking forward to reading what direction other folks take this question in.
This is a great answer IMO. And it really paints the picture of what kind of dev you are: mature enough to know that "it works" doesn't necessarily cut it, experienced enough to visualize what else remains to be done, persistent enough to get it across the finish line. I think those are essential traits in a senior dev.
Have to agree. Putting that time and effort in is no joke, especially when the fun part is already long done.