3 ms·
Currently in a job where code quality is not even considered a low priority, but a waste of time. I'm now on week 6 of attempting to complete a "simple" HTML p
by denkmoon 5y ago
Currently in a job where code quality is not even considered a low priority, but a waste of time.
I'm now on week 6 of attempting to complete a "simple" HTML page update. Piles of documentation around, but none of it useful or relevant. So I have to work out how the system works from looking at code, but the code is so damn bad every time I think I know what I need to do, it turns out to be wrong.
The people who know what to do left many years ago, of course.
- yxhuvud 5y agoI would recommend you get into the habit of making small improvements that fly under the radar while doing other tasks. It may not fix big architectural issues, but it will still help with making the code base more understandable and less brittle.
- denkmoon 5y agoThe improvement I'm making is searching for a new position :) Can't help those who won't help themselves.
- gunshai 5y ago:( I am currently in a similar situation but it is all scripts on an industrial data historian intertwined with DB updates. When the previous hire gave notice he had 2 weeks to document what took many people more than 5 years of effort to piece together. I won't call this hell, but at least my manager and boss have very tempered expectations. Edit: I'll be sending this article out to my co-workers in the morning with some snippets.