Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

374

I'm talking about the idiots who decide to over engineer software to insanity. Like yes, I understand proper architecture and engineering. No, i dont agree that every single module has to be engineered to perfection. Also these same assholes are usually the people who routinely ignore their own code standards, and try bugging me to quick approve their clearly not good looking code. Than they come back and nit pick over mindless idiotic pedantics.

I'm talking about the idiots who decide to over engineer software to insanity. Like yes, I understand proper architecture and engineering. No, i dont agree that every single module has to be engineered to perfection. Also these same assholes are usually the people who routinely ignore their own code standards, and try bugging me to quick approve their clearly not good looking code. Than they come back and nit pick over mindless idiotic pedantics.

(post is archived)

[–] • 6 pts

Coding well was once an absolute must due to hardware limitations. Coding is shitty af now because the hardware can handle unoptimized garbage.

[–] • 4 pts

Terry Davis was right.

[–] • 4 pts

That guy wasn't crazy, he managed to create an entire OS from scratch, you have to be fucking smart to do that. Most people can't even understand how the bootloader on the OS works, let alone write on

[–] • 2 pts

It's possible to be smart and crazy at the same time.

[–] • 2 pts

dont forget the whole 'this function name is problematic and needs to be changed for feelings' and 'please to be repeatings vat it is you like me to do sir' things...

[–] • 2 pts

"'Master' is racist"

[–] • 0 pt

POINT OF ORDER! POINT OF ORDER!

STOP USING GENDERED LANGUAGE! IT IS TRIGGERING!

thankyou comrade

[–] • 3 pts (edited )

I don't work with engineers anymore, but I know a couple and they do the same bull crap in non-work life. If you correct them on something they come back at you nit picking at stupid nonsense or they will just play dumb and not accept your correction by using some lame excuse. Many engineers cannot accept the fact they don't know everything.

[–] • 3 pts

The nitpicking is what gets me. A good example, this one guy didnt like a piece of code i wrote. I wrote a dummy array to make it more generic for other uses. I thought to myself, a dialog can be generic, because it can be used for other purposes beyond the initial application. So i passed an array with three properties per model: label, value, priority.

Not good enough, instead i have to now inject 4 different services, add in a querying system, some asynchronous calls, and a bunch of stuff, so we can remove the logic details from the caller requesting said dialog. Except, in this case the caller IS responsible, because the dialog should not contain business logic beyond projecting the view models. So now this dialog is becoming a monster because nitpicker is being pedantic

[–] • 2 pts

Egotism is a huge problem. Both the NiH syndrome and "I'm special, so I'm exempt from my own rules and best practices" is a big problem.

Over engineering was pushed mainstream with java. Now everyone thinks they need ten levels of abstraction because they think they might need to use this code slightly differently ten years after it's no longer in use.

Made worse is too many people completely loose sight of context. Best practices at Google doesn't apply to 99% of the coding world. What makes sense for them is stupidity for the majority.

[–] • 1 pt

You see this paradigm a lot between the back end and front end world. I have worked on backend systems, and a lot of time, there was a lot of focus on what is right, vs what works. In front end world, it's a roller coaster of just saying fuck it, and doing whatever you want because the framework will take care of it. At my current company, they used an alpha stage technology from Microsoft. As of current, there is no live reload, no error parser, no real linter, no interaction between forms, plaguing bugs everywhere, limitations of the framework causing blockers. But hey, apparently this was the best solution available ...

[–] • 1 pt

I feel it.

"New and shiny is always better."

[–] • 1 pt

Reusable software is almost never reused. And the extra effort to write, review, test, and debug is bad tradeoff.

[–] • 1 pt

This is the correct answer. I have rarely seen any of these conventions lead to any sort of productivity increase. I was talking to my new job, and we both agreed that over abstraction is dangerous, since it can give too much information about architecture. This is also very true of the current micro services architecture trend, where you have an endpoint for everything

[–] • 1 pt

Yup. And the constant re-writing of the same thing over and over and over again in new languages.

The whole thing is just duct taped together.

[–] • 0 pt

It's better than permabeta, and in large projects it's absolutely essential. I think you just don't want to take the time to write proper code.

[–] • 0 pt

Man.... if these fuckers are pushing 'engineered to perfection' in software they need to fire themselves.

[–] [deleted] • 0 pt

Okay, just a regular dummy here with an honest question.

Last time I did software, it was punch holes on cards. Yeah, it's been a while.

My question is simple and honest: Why do 'coders' call themselves engineers? We didn't. Do engineers have college degrees or something? Please enlighten my feeble old brain. Thanks!

[–] [deleted] • 0 pt (edited )

It just depends go to a place where everyone writes everything in python and every app is a Gordian knot where even the people who wrote the stuff dont know where any specific functionality lives. Then have numerous type specific errors wreak havok on your database structures.

[–] • 1 pt

And.... you are not kidding, it is really like this

Someone tell me that this is going to survive a mild system hickhup ?

Naaaaa

[–] [deleted] • 0 pt

Oh you I see you are familiar with Azathoth, sometimes called "The Blind Idiot God" and the "Nuclear Chaos"

[–] • 0 pt

Your coders create the DDL?

Why not a DBA create the DDL and coders comply with it?

[–] [deleted] • 1 pt

Because then theres the whole argument over who controls the domain logic does the database or does the application. What ends up happening is it bifurcates into two silos then your back to the problem of not knowing which piece contains which logic and also it becomes lovely when the two layers get into a fight.

[–] • 0 pt

I'll take how are engineers like women for $500 Alex

[–] • 0 pt

Software engineering is slowly but surely being kiked out to what essentially amounts to regulatory capture.

It's fucking retarded.

[–] • 0 pt

Also these salaries are not sustainable, especially in the larger companies, paying upwards of 200K+. It's going to crash and burn at one point