To me, this sounds more like a project management/culture issue rather than a development issue. Due to any of the following.
Extremely difficult testing and approval of changes post-launch. AKA: the waterfall model
Customer refuses to pay for maintenance or tweaks, only new features. So management will never allocate time for it.
High company turns over (due to other reasons), and lack of issue tracking. So the "todo" is forgotten.
All the reason above has less to do with development and more of project management which the team with discipline can work on.
Unfortunately, one that is all too common in many places. And has somewhat rightfully gained its place as a "truth" or "rule of thumb". Something I hope will improve in time.
Its probably also driven by the young developer desire to produce the best code ever, now. Instead of a solution for the user.
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.
To me, this sounds more like a project management/culture issue rather than a development issue. Due to any of the following.
All the reason above has less to do with development and more of project management which the team with discipline can work on.
Unfortunately, one that is all too common in many places. And has somewhat rightfully gained its place as a "truth" or "rule of thumb". Something I hope will improve in time.