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.
True, that is surprising and makes everything worse. It’s probably controlled by a setting that none of those engineers knows how to change, based on the lack of knowledge described here.
My guess is that a stack trace is being generated, but something further down the chain is consuming it, realizes there’s an error, and just throws -1 instead of the stack trace itself.
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.
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).
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.
It’s a bit sad, but not that surprising, that if this is true then Microsoft is clearly not tasking their most experienced engineers on the control panel (you know, that part of the OS who’s function is to allow you to tweak all the rest of the OS?).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
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.
The complete lack of error reporting in the compiler is a surprise though.
True, that is surprising and makes everything worse. It’s probably controlled by a setting that none of those engineers knows how to change, based on the lack of knowledge described here.
My guess is that a stack trace is being generated, but something further down the chain is consuming it, realizes there’s an error, and just throws -1 instead of the stack trace itself.
Something like
But did you read the last line? This isn’t classic control panel, this is the new control panel.
Same shit trying to implement with systems on the backend older than a lot of people using them today I’d imagine
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.
Yea, this doesn’t sound horrible for what it is. Plenty of Linux systems are this bad.
Plenty of UI applications* are this bad
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
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.
It’s a bit sad, but not that surprising, that if this is true then Microsoft is clearly not tasking their most experienced engineers on the control panel (you know, that part of the OS who’s function is to allow you to tweak all the rest of the OS?).