Great post, one can clearly tell you talk from experience.
Identify when you have maybe done something pretty rushed and flimsy.
100% this. I'm for always trying to "write things right" and take a bit more time to really carve a solid solution. That's not always possible, and it's not only due to time constraints, which is the most common reason (and sometimes, excuse).
Sometimes we're not really fully sure of the right solution. Maybe the problem is too new to understand it deeply enough, so we come up with a solution that's half baked or clearly imperfect. I don't see it as a problem unless we just accept it as is and forget.
In these cases i create a tech debt ticket on the board and make sure it's addressed in due time. The key being to be honest with ourselves and openly admit a better solution needs to be found.
Anyway it was a refreshing read, really enjoyed reading and finding myself nodding at pretty much every point you mention.
I'm a Senior Developer and Co-host of Friday Night Deploys Podcast. I'm also a dad that likes to play video games and lift, always failing to keep it real with the kidz.
Great post, one can clearly tell you talk from experience.
100% this. I'm for always trying to "write things right" and take a bit more time to really carve a solid solution. That's not always possible, and it's not only due to time constraints, which is the most common reason (and sometimes, excuse).
Sometimes we're not really fully sure of the right solution. Maybe the problem is too new to understand it deeply enough, so we come up with a solution that's half baked or clearly imperfect. I don't see it as a problem unless we just accept it as is and forget.
In these cases i create a tech debt ticket on the board and make sure it's addressed in due time. The key being to be honest with ourselves and openly admit a better solution needs to be found.
Anyway it was a refreshing read, really enjoyed reading and finding myself nodding at pretty much every point you mention.
Glad you enjoyed the read! I very much agree about not always being able to fully come up with the right solution.
I've come away from code proudly and sometimes it holds up which feels great, and sometimes I've come back thinking "What is this trash?".
It's a fine line between rushing out bad code or paralysis from obsessing over the best solution.
With experience of the specific problems and expectations I think this widens but always has room for this error.
Always being honest too is an excellent point!