I don’t think this is legit because even as I was reading it, I was expecting it to sound a lot worse than it ended up sounding. Like, it didn’t sound great or anything, but it didn’t sound nearly as fucked up as I would expect firsthand descriptions of piled-on legacy code to sound after almost 50 fucking years.
Seriously, it doesn’t sound great, but it sounds about what you might expect wiring up a new UI widget in WPF or whatever the latest thing for native Windows is. Sounds like what would happen if you started developing a Windows app using the Microsoft scaffolding and never applied any kind of software architecture beyond that and it just grew and grew into a big ball of mud. Exactly what I would expect given the quality of so many of their frameworks, and I say that as a professional dotnet software engineer.
Sounds like classic junior engineer shit. “Let’s do a big rewrite!” Followed by everything going to shit because they don’t how to create good maintainable software architecture and for whatever reason there weren’t enough senior engineers around to show them the way.
What cracked me up was all that copying blocks of code “because no one knows how anything works”.
That reeks of novices copying code without bothering to read it well, and since this work method is horrendous, no one stays enough to stablish a proper knowledge base.
Complicated code is when 700 projects are all entangled and when you add a 3D bar for measuring purposes (it was just a bar like 100 nanometers long so you could get a feel for size in 3D scans, in the 3D viewer), the up (not the down) mouse scroll stopped working for sliders in all the 2D GUIs…
That is crappy code and I was there when we got that bug (Avizo software).
I don’t think this is legit because even as I was reading it, I was expecting it to sound a lot worse than it ended up sounding. Like, it didn’t sound great or anything, but it didn’t sound nearly as fucked up as I would expect firsthand descriptions of piled-on legacy code to sound after almost 50 fucking years.
Seriously, it doesn’t sound great, but it sounds about what you might expect wiring up a new UI widget in WPF or whatever the latest thing for native Windows is. Sounds like what would happen if you started developing a Windows app using the Microsoft scaffolding and never applied any kind of software architecture beyond that and it just grew and grew into a big ball of mud. Exactly what I would expect given the quality of so many of their frameworks, and I say that as a professional dotnet software engineer.
But did you read the last line? This isn’t classic control panel, this is the new control panel.
Sounds like classic junior engineer shit. “Let’s do a big rewrite!” Followed by everything going to shit because they don’t how to create good maintainable software architecture and for whatever reason there weren’t enough senior engineers around to show them the way.
Same shit trying to implement with systems on the backend older than a lot of people using them today I’d imagine
And “the specific resource ID” is almost certainly for localization of the text
What cracked me up was all that copying blocks of code “because no one knows how anything works”.
That reeks of novices copying code without bothering to read it well, and since this work method is horrendous, no one stays enough to stablish a proper knowledge base.
Yeah this is classic legacy code.
Complicated code is when 700 projects are all entangled and when you add a 3D bar for measuring purposes (it was just a bar like 100 nanometers long so you could get a feel for size in 3D scans, in the 3D viewer), the up (not the down) mouse scroll stopped working for sliders in all the 2D GUIs…
That is crappy code and I was there when we got that bug (Avizo software).
W H A T
Yea, this doesn’t sound horrible for what it is. Plenty of Linux systems are this bad.