WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2026 Poal.co

512

This is something ive noticed at my own job. They decided to create this flagship product using a completely exprimental Microsoft stack. How experimental? No intellisense support on the pages, no live/auto reload, no linters/parsers for 50% of the code base, json files everywhere. Just a complete mess. Now im just getting frustrated, because the linters say one thing, and then the code base blows up. But more importantly, this comes off as a massive case of complete overkill. What was wrong with a REST API and divorced front end? You know, the industry standard since 10 years ago. But no, lets go and reinvent the wheel with some insane product line.

I once interviewed with Microsoft, and they were laughing at the fact someone was using this product line in a production setting. Like they thought i had just said a bad joke or something.

This is something ive noticed at my own job. They decided to create this flagship product using a completely exprimental Microsoft stack. How experimental? No intellisense support on the pages, no live/auto reload, no linters/parsers for 50% of the code base, json files everywhere. Just a complete mess. Now im just getting frustrated, because the linters say one thing, and then the code base blows up. But more importantly, this comes off as a massive case of complete overkill. What was wrong with a REST API and divorced front end? You know, the industry standard since 10 years ago. But no, lets go and reinvent the wheel with some insane product line. I once interviewed with Microsoft, and they were laughing at the fact someone was using this product line in a production setting. Like they thought i had just said a bad joke or something.

(post is archived)

[–] 0 pt

I wouldn't go so far as to say software engineering isn't engineering, but it's definitely a different field then classical, Newtonian Physics engineering.

I also think the culture around software engineering is a problem, and a big part of when engineers fucking suck now.

A lot of the techniques used in software development just don't translate well mechanical/structural/electrical/whatever else.

A perfect example is design of experments. Sure, that shit works great when you can run thousands of iterations on a computer, and if something fails, you just restart. However, when you start trying to run DOEs on physical components, which need to be built, installed on testers, and run through however many cycles you need, it's just not practical to get enough iterations to have a meaningful data set.

And simulation man, fuck I hate simulation. Sure, there is value in using it, but without physical testing to verify the output, it's really easy to get lead down a dead end.

Also, if you can't simulate the hungover dude in the plant in Mexico that is actually going to manufacture the component, I would question the validity of your simulation.

At the end of the day, I blame millennials. My first engineering job was a bunch of old dudes who did amazing sketches with calculations on fucking engineering paper, then wrote memos to file to document the results. Since then, it's basically been a bunch of late 20s/early 30s morons who couldn't write a memo if it saved their life. They spend more time creating models based on empirical data then the do actually understanding how their component works.

Fuck this shit. Sometimes I wished I had just kept laying brick.