Perfection prevents progress. Can't improve your code if you don't get it working in the first place. Programming itself is an iterative process and it's fine to "fix it in post". Definitely don't want to get buried in technical debt though.
Even teams forget this at times. My team was trying to duplicate a chunk of functions that worked on another project, using the overly optimized code we wrote for it.
After a few days of failed attempts, someone said. "Screw this. Let's just hardcode it." Just to get something to work.
Once we got something to just "work", then we slowly moved to making it as tight as the code we were trying to duplicate.
It's a excellent reminder... No matter how many years of experience.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Perfection prevents progress. Can't improve your code if you don't get it working in the first place. Programming itself is an iterative process and it's fine to "fix it in post". Definitely don't want to get buried in technical debt though.
If I had to write perfectly clean code while getting it to work, I would never get anything done.
Also, if the requirements change while you're working on a feature, all the "perfect" code you wrote might not be useful anymore.
Wow that’s something I’m working on I want everything to be perfect and that’s not realistic all the time.
Even teams forget this at times. My team was trying to duplicate a chunk of functions that worked on another project, using the overly optimized code we wrote for it.
After a few days of failed attempts, someone said. "Screw this. Let's just hardcode it." Just to get something to work.
Once we got something to just "work", then we slowly moved to making it as tight as the code we were trying to duplicate.
It's a excellent reminder... No matter how many years of experience.