HNHacker News
TopNewBestAskShowJobs

throwaway_8462

21 karma · joined January 13, 2024

submissionscomments
throwaway_8462··on Stellarium: Software which renders realistic skies in real time
> Not sure why this post is anonymous

Honestly, my work place is filled with inexperienced people who have decided what the right approach should be. I'm older and more experienced than most and have learned that I can't win all battles, and bite my tongue when I see them making bad decisions. It's a form of age discrimination where even the management thinks that "young people see problems with fresh eyes". I don't want to come across as an "ok boomer" developer stuck in their old ways. "Rewrite everything in the new untested framework? Sure why not. The code is over 2 years old, so it's full of crusty legacy code".

I may seem a bit bitter in my comments, but I'm mostly disillusioned and are trying to see it as a learning experience. I'll give my opinion sometimes, and if they don't follow it it's not my problem. They will just need to learn the hard way and will probably end up in my situation in a few years.

I'm just collecting my pay check and planning to move on to a work place with more balanced demographics.

throwaway_8462··on Stellarium: Software which renders realistic skies in real time
I think it also is a measure for technical debt. If someone can easily understand the code and make changes, it is a sign of low technical debt.

Too often developers measure code quality by applying personal subjective measures, like number of lines per method, DRY or choice of programming language and start making major refactoring based on personal preferences.

If someone without knowledge of the code can swoop in and make meaningful changes, it does not matter how many lines of code there is or if it is built with X or Y. It's the end result that matters.