This fucking guy create a mess of a code, more than a spaghetti code, a clusterfuck of shit untested spaghetti code, and the project is actually getting well, our customer is getting bigger but everytime there is something to be added, its a fucking pain to add, and when something breaks, almost every thin breaks, and the shitty guy who wrote this code is quitting and its fucking up to me to clean up all the fucking mess, fucking asshole.

DOCUMENT AND TEST YOUR CODE KID, DONT BE A FUCKING SPAGHETTI PROGRAMMER

What languages are you using?

@black-kite php, the project were using is in laravel

@pikunb0ss is the pay worth it at least?

@iSwimInTheC it is

Laravel even tries to push you in some structure. If you manage to break that severely it's indeed way worse than normal spaghetti.

I had a tram mate that i provided with an abstract class. Only thing needed was a nice derived class with a method override and calling the conductor/method properly.
He managed to hack the method so it set the constuctor input from global variables and code. Functions in multiple files where called instead of implementing it in the class. The constuctor was just initialised with null. The dude was actively fighting the framework (message queue)

@hjk101 what the hell!!? Dude needs to take a class or something.

@iSwimInTheC he can do way better. He just felt it was a one off script and already started a crappy implementation before we got to the triggering it by queue message. So he just continued that way and that actually needed to run in production.

When I needed to change it I had many WTF moments. It was a crucial part in the
subscription system and just plain unprofessional and dangerous. He did get some flak for that one.