Manager: 'Please remove this checkbox from that page.'

Me: 'Sure thing, it was stupid anyway. Just gimme a couple of minutes.'

Legacy code: 'LOL the checkbox is wired to everything else and if you simply remove it the backend will shit itself. There is several hundred lines of inline Javascript in the HTML template with some Thymeleaf stuff managing the form data or just are there to make the code less readable. The controller for the page is a bit more than a thousand lines of spaghetti, no easy way to find where is that specific data necessary and where can be easily removed. Class variables declared between methods, dozens of nested if statements checking shit in every method and the data is passed through like half a dozen other classes. Good luck with that!'

Me: '💩.'

Most business apps end up being overcomplicated and convoluted because that’s what most businesses are:

Overcomplicated and convoluted.

Building an app to operate systems like that will always be an exercise in garbage in garbage out. Fix your process before saying wE nEeD An aPp To Do ThIs. You don’t need an app. You need a smack upside the head.

When the code is so spaghetti that just wish you could make bolognese with it

what kind of dumb fuck you have to be to get the react js dev job in company that has agile processes if you hate the JS all the way along with refusing to invest your time to learn about shit you are supposed to do and let's add total lack of understanding how things work, specifically giving zero fucks about agile and mocking it on every occasion and asking stupid questions that are answered in first 5 minutes of reading any blog post about intro to agile processes? Is it to annoy the shit out of others?

On top of that trying to reinvent the wheels for every friggin task with some totally unrelated tech or stack that is not used in the company you work for?

and solution is always half-assed and I always find flaw in it by just looking at it as there are tons of battle-tested solutions or patterns that are better by 100 miles regarding ease of use, security and optimization.

classic php/mysql backend issues - "ooh, the java has garbage collector" - i don't give a fuck about java at this company, give me friggin php solution - 'ooh, that issue in python/haskel/C#/LUA/basically any other prog language is resolved totally different and it looks better!' - well it seems that he knows everything besides php!

Yeah we will change all the fucking tech we use in this huge ass app because your inability to learn to focus on the friggin problem in the friggin language you got the job for.

Guy works with react, asked about thoughts on react - 'i hope it cease to exists along with whole JS ecosystem as soon as possible, because JS is weird'. Great, why did you fucking applied for the job in the first place if it pushes all of your wrong buttons!

Fucking rockstar/ninja developers! (and I don't mean on actual 'rockstar' language devs).

Also constantly talks about game development and we are developing web-related suite of apps, so why the fuck did you even applied? why?

I just hate that attitude of mocking everything and everyone along with the 'god complex' without really contributing with any constructive feedback combined with half-assed doing something that someone before him already mastered and on top of that pretending that is on the same level, but mainly acting as at least 2 levels above, alas in reality just produces bolognese that everybody has to clean up later.

When someone gives constructive feedback with lenghty argument why and how that solution is wrong on so many levels, pulls the 'well, i'm still learning that' card.

If I as code monkey can learn something in 2 friggin days including good practices and most of crazy intricacies about that new thing, you as a programmer god should be able to learn it in 2 fucking hours!

Fucking arrogant pricks!

Best: actually started to work on side projects, they are not just discarded ideas on the paper anymore, so excited about this one

Worst: legacy bolognese app nobody understands and doesn't have documentation coupled with weird API also without any documentation

Ah good ol' refactoring summer.

*Me starts refactoring spaghetti bolognese*

- Hurrah everything can be generic and so much better. I'll just do this and this and this and this, oh and this also needs to be reworked cuz of this.

8 hours later.

- it wasn't that bad!

$ git status

- oh god

$ dotnet test

- welp.... I need something to do tomorrow.

That LOL feeling when incompetent backend wants you to fix their bug on the frontend!

How about NO!?

And why tf I know more about how backend works on this system than devs that are actually working on it???

Genuinely asking some rare pokemon php developers that are up to date with the tech (all php devs I know stopped learning when my grandpa was like 5 years old) to show me php code that is not spaghetti bolognese. I am asking this as I am yet to witness such code for the first time in my life (and I am coding since 94')!

Cool project, cool people, but everything-just-works™ code makes it hard.

Every component has its own logic for the things that are already made, every table has its own filters and those filters are the same piece of code in every component.

I'll complain about this shit tomorrow as today I spent my day making a fucking table work, can't even copy the shit as it has its own intertangled logic that doesn't make any fucking sense.

Yesterday I ate Bolognese, today I'm working in one.

Lol the funniest thing Iis that dude who wrote this piece of shit is gonna review my code, can't wait for that call.

And yeah useMemo() on every fucking function. Functions pulling shit directly from state and returning it straight away...

Literally this:

const filteredData = useMemo(() => { return stateData }, [stateData])

Ok, what the actual fuck.

The weirdest wtf was that typescript is used as it should, like every case covered correctly. Not sure if gpt or just dumbasses working on this pos.

The term 'continuous rot' just came to mind as something like this: A lone/sole developer is hired to implement a solution but dispite the illusional good intent shared by everyone at the beginning, time constrains will soon come into play and the code deteriorates at a rapid pace until the developer can't handle it anymore... But someone else comes to continue the work... And the rot continues... And once again... And again...again....

Anyone?

It seems they mistaken me for italian giving me spaghetti all over the product. Go to frontend to check the app, react with weird jQuery, no routes, pages summoned by the templates that have concatenated values and html in vanilla js, changing screens/pages with jQuery, no router... ok lets see the other app, react, redux, offline capabilities and tought myself niicee hut nothing work as intended with clusterfuck of hacky workarounds that makes app look like it is working but with hardcoded data. Offline means automatic sync when you get the network back, right? Oh backend never developed any sync, so you guys can do it, we have to fix and patch some important stuff! I don't like php but whatever, let's see what is going on there... So much spaghetti bolognese there that Bologna actually called to ask if they can buy some, they are out of stock because of us!

This is just like that song mess.css from stdout, but in any file you open!

Living on deserted island eating grass and coconut for the rest of the life doesn't seem so bad atm!

Joined a new project.
The core of the application has references to pretty much everything in the entire codebase, both api and database layer.
On top of that it uses extension methods instead of mappers or normal methods on classes in order to "keep classes short", so many methods are unnecessarily hidden from view.

Tried to fix it, got told to revert back to the old version because "it might be wrong, but at least it's wrong everwhere". Guess I'm making bolognese for dinner.