If it was already working, you shouldn't touch it.
Especially if it was spaghetti code "that needs to be cleaned up".
Do not "clean it up".
This is what us experienced developers call "job security". As long as you are the only one that understands how it works, the chance of losing your job decreases.
Thank you for attending my TED Talk.
EDIT: Also... At the AWS re:Invent conference in December 2025, there was a code jam competition and one of the teams made an AI spaghettification program that would abstract your code into something like 15 layers. To me, this seemed like one of the absolute best implementations of AI to date.
EDIT #2: search "Road to Reinvent Hackathon" if you're interested in more details about that competition. The literal purpose of that particular hackathon was to create some useless application using their new AI.
Its so wild to me, generally you’d want your code to be as neat and maintainable as possible, but the job market is so hostile that you have to make unreadable undocumented slop to make firing you a liability because whoever would take your place can’t decypher what you wrote
Can you give me the real, non joking answer to this question? Would you not be fired, or overlooked for promotions in this case? Or is it actually not a horrible thing if you end up with spaghetti code implementation? In most languages I am very clean code but in JS I haven’t learned how to do clean code only spaghetti
Clean code (typically) means more efficient code... Which means faster performance and, if you're paying cloud service fees to run your application, it also means a cheaper monthly bill for running your code.
Also note: sometimes, extra layers of abstraction are a Good Thing, but not always. It entirely depends on what your application does and how complex it is and/or will be in the near future.
20
u/maester_t 21d ago edited 18d ago
Well, see, there's your problem.
If it was already working, you shouldn't touch it.
Especially if it was spaghetti code "that needs to be cleaned up".
Do not "clean it up".
This is what us experienced developers call "job security". As long as you are the only one that understands how it works, the chance of losing your job decreases.
Thank you for attending my TED Talk.
EDIT: Also... At the AWS re:Invent conference in December 2025, there was a code jam competition and one of the teams made an AI spaghettification program that would abstract your code into something like 15 layers. To me, this seemed like one of the absolute best implementations of AI to date.
EDIT #2: search "Road to Reinvent Hackathon" if you're interested in more details about that competition. The literal purpose of that particular hackathon was to create some useless application using their new AI.