Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
If Gordon Ramsay made code reviews, I would watch that show. Especially the insults he would use for handling clients.
"This code has so much spaghetti, it decided to open it's own restaurant"23 -
If you see someone coding at mcdonalds, starbucks etc.
"Excuse me, would you like a fork for that spaghetti"14 -
Me: Can you make me some meatballs?
Engineer: No, what are you talking about?
Me: I thought you were a chef.
Engineer: I'm not a chef, what made you think that?
Me: I was looking at your code and I haven't seen that much spaghetti since Olive Garden ran the endless pasta special. I was just wanting some meatballs to go with it.5 -
How it should be:
- First: solve the problem
- Second: Write your code.
How many people do:
- First: Write code
- Second: solve code problems
- Third: Adapt code with requirements
- Forth: get lost on your spaghetti code
- Sixth: make a suicide8 -
Imagine what a coder Gordon Ramsay might be like:
Your alghoritm is so FUCKING slow, I'd rather to try to brute force a 20 characters long alphanumeric password!
This app is more insecure than an average teenager!
If your code was a spaghetti it would be a fucking health hazard!14 -
After finishing up 70% of a feature,
Brain: "there's a better way to do it"
Me: "ok ill just change a bit of code here and there.."
-- 2 hours later --
swimming in spaghetti code..7 -
Boss: please refactor this js 2k lines spaghetti code class and use it in our reactive functional app
Me: it will take like 1 week to refactor and plug this
Boss: but it's almost the time I needed to write it!
YOU DON'T SAY? MAYBE FIRST LEARN HOW TO WRITE DECENT CODE. ffs.2 -
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: '💩.'5 -
When people paste their whole fucking million line noobie spaghetti code into a single Stackoverflow question:
6 -
When your colleague, who wrote the API is on vacation, the documentation is non-existent and you are tired from reading all-day long his spaghetti code, so you are just waiting for him to show up.
2 -
Rewriting code you wrote as an intern a year ago that has been rewritten by another intern in the meantime...
The joys of spaghetti code and experience.1 -
"I want my API to return insults as error messages if they forget shit"
Uh no, I prefer helping them out by writing proper documentation than sending a giftbox with me flipping them off like Linus Fucking Torvalds for their spaghetti usage of your API5 -
Arrived at a game jam in an animation school. I hope they're better at game design than they are at cable management :)
7 -
Yo.
His palms are sweaty
Knees weak arms are heavy
Bugs littering his code already
Cold spaghetti 🍝
He’s nervous but on the surface he looks calm and ready to git push
(Hit a blank with thinking of code-related lyrics, anyone got ideas?)16 -
One team was delivering for 12 months.
... but definition of done not met. Code crap everywhere. Tests barely there and are total mess.
I inherited mess after previous lead engineer.
I exposed all the issues to the management in a straight way, no sugar coating.
... and now guess who's the bad guy for "complaining" instead of shut up and "making it work"?
P.s.
"Giving accurate report about situation" is seen as "complaining".7 -
I have just concluded a post-mortem on one of my servers.
Cause of death: out of memory due to a tiny memory leak in a VPN service triggered by 66 different IPs brute-forcing the creds at the same time. Mostly from China, of course.
Dear bot writers: you made me put aside my spaghetti and write iptables rules. I hate iptables. And I love spaghetti. You should be ashamed of yourself! Did momma not teach you basic OpSec? Don't crash the target and never, ever, interrupt the sysadmin during dinner!6 -
That moment when you have a tight deadline, but your inner *developer dignity* won't let you write code that sucks.5
-
Fucking hell, the devs before write a query that pulls 30ish column for a report. When I break it down MANUALLY, since it’s a spaghetti on top of another spaghetti, you only need 6. Fuck you, did you dropped your head when you was a kid? Fuck sake, and every query is written in stored procedure even though you’re using an entity libraries19
-
Yo, his palms are sweaty
knees weak, conscience heavy
There's commits on master already:
Your mom's spaghetti code19 -
Last year I signed in for a course called "Best Practices in Programming", and part of the course was to get the code of our current projects reviewed by a professional developer. I had a horribly written (out of inexperience) code in Python. The guy who had to review my code basically said I had no idea about coding but went on helping me a lot. Since then I started to learn some concepts of software engineering, how to code more efficiently, and so on and I've been much better ever since. So kudos to him for putting up with my spaghetti code and sending me in the right direction!1
-
Give me a 10 year old application with no comments, layers of spaghetti code, global variables, embedded SQL, and a text editor with no debugging; just don’t make me write Excel formulas.6
-
!rant
I just wanted to tell you guys:
That after a month or so working on a spaghetti pile of codes, our team finally decided to study and use Git for our project.
I'm so happy right now 🎉2 -
The bossman asked if our signup service sends an automated email after we successfully process someone's payment or when we promote them to full customer.
That sounds like a simple query, yeah?
Well.
Here's some background:
We have four applications; one in React, three in Rails. I'll replace their names to retain some anonymity.
1) "IceSkate" is the React app, and it's a glorified signup form. (I wrote this one.)
2) "Bogan" is the main application, and is API-only; its frontend has been long since deprecated by the following two:
3) "Bum" is a fork of "Bogan" that has long since diverged. It now contains admin-only tools.
4) "Kulkuri" is also a fork of "Bogan" that has long since diverged. It now contains tools specifically for customers, which they can access.
All but IceSkate (obv) share a database.
Here's how signups happen:
Signups come in from IceSkate, which hits a backend API on Bogan. Bogan writes the data to the database, charges the card immediately, and leaves the signup for moderation.
And here's how promotion from signup to customer happens:
Bum has a view allowing admins to validate, modify, and "promote" a signup to a full customer. Upon successful promotion, Bum calls "ServerWrap", a module which calls actions on the other applications; in this case: Bogan.
Bogan routes execution through three separate models before calling "ServerWrap" again, this time calling KulKuri.
Finally, KulKuri actually creates the customer!
After KulKuri finishes creating the customer, execution resumes on Bogan, which then returns, causing execution to resume on Bum. Bum then runs through several other models, references the newly-created customer object (as all three share a database), and ... updates the customer with its current data, and then updates the signup object. After all of this, it finally shows the admin the "new customer" view.
It took me 25 minutes to follow the chain of calls, and I still don't know quite what's going on. I have no idea if any of it sends an email or not -- I didn't see any signs of this, but I very easily could have overlooked something.
So, to answer bossman's question... I asked the accounting people if they send the email manually. If they don't, it's automatic, which means I missed something and get to burrow through that mess all over again!
I really hope I missed something; otherwise I need to figure out how and where (and when!) to send the email...
just...
errrrgghh9 -
Your code has so much spaghetti, there's vomit on my sweater already.
(reposted as a rant cos @yatanvesh said so)4 -
tl;dr @Root refactors some spaghetti.
I'm refactoring an api that creates a support message. It's a post route.
When seeing a magic hardcoded message string, this route instead updates the user object, and does not create a support message.
It also returns different results if the user is muted (fine) or if saving the message succeeds or fails (fine).
But if the user is creating a duplicate message, it doesn't save the message (fine) and... redirects to listing their messages instead? Wat?
Also, when refactoring this (migrating to a new message backend), I discovered that not all routes return a response. If the message is a non-duplicate, from a non-muted player, from a non-redacted client, the route doesn't respond at all!
So, I'm having fun cleaning this up. I actually am. Except I'll need to support all of the legacy clients for the next lifetime or two. I mean, really. There are still people with Android v2 devices who are using this thing. not even kidding.9 -
Slow, old, spaghetti coded legacy projects that no one has touched for years.
You know those ones where you put your Indiana Jones hat before going in and barely come out alive.2 -
Microsoft Excel - it created a generation of business analysts who think just because they can write convoluted spaghetti logic in excel that it makes them a programmer.5
-
"Mature codebase"
"Our entire team are senior devs"
"Almost everyone that worked on the project is still here and available, so nothing's lost! We can ask whatever we need to."
You would think this would mean the code was clean and easy to read, and you could ask the person who wrote it for help. But. no. It's kinda the opposite.
Here's an example:
I'm trying to write a mailer, and I have no freaking clue how to get it working. I talked with two of the more senior devs, and both assured me it was very straightforward, and then walked me through the quite complicated mailer structure and got lost. The first pretended not to, but glazed over a few holes in his tour, and said I could figure the rest out. The second one ended up admitting that he's totally unfamiliar with it -- his last commit on a mailer was from about 8 years ago -- and doesn't know how to get it working anymore.
So, I'm on my own.
I wrote a super basic mailer for debugging (no idea if/how it actually sends a mail, but I think I can construct one?). But whenever I call the mailer, it gets run twice? Somehow? Apparently I need to start a bunch of daemons to get that part of the system to work. Which is cool because they don't work fresh out of the repo. Got some further help, and now my ostensibly working code throws errors for an undefined var that i'm not even using, and to make it easier: without a backtrace. joy! There's so much inheritence and extending and including going on that it's going to take me hours to track this down. ugh.
I'm keeping my paystub in front of me for some desparately needed motivation.13 -
Soooo, i'm assigned to finish a half made prototype of a production line functional test platform.
1 - Some wires were faulty so someone decided to change them.
2 - wild shortcut appears *music fades, screen goes black*
3 - now i have to fix the prototype
4 - Devil's voice whispers on my ear *welcome to heeeeellllllll*
22 -
You would think for a company as big as Google they would be able to write good fucking documentation but nope!
Fuck me it's more spaghetti than my code!4 -
I left some spaghetti code on production at the company i left, i really hope my replacement isn’t a psycho who’ll try to find me3
-
So, should I refactor this into a .greatGreatGrandParent() method, or should I just go hang myself?
(Thanks former colleague for this gem)
10 -
All front end written in one file. File has over 6000 lines, mix of a php, javascript and extjs. It kills my IDE.5
-
That feeling when you refactor that spaghetti mess into clean beautiful code that passes all tests flawlessly4
-
Fuck you stupid cunt!!!! If your fucking project depends on empty folder structure just put a fucking gitignore file on it so I don't have to waste all fucking day debugging your tasteless spaghetti to figure out that you download files to an empty folder that git clone doesn't create.3
-
Ticket: Allow merchants to customize how their Wallet Passes look! It’ll be super easy, just add these nine merchant-modifiable strings (they support vars) and use their contents for text instead of what we use now. Simple!
Reality: There need to be 24 strings, there are some rules I can’t convey to the merchant (because the system literally does not include instructions, only a name and a textbox), the code to generate the wallet pass is inefficient, uncommented, branching spaghetti that I’ll need to rewrite (it seriously generates every possible field, and then only uses the ones it needs), the specs are so much worse, and half the default values they want aren’t even possible. As in, I don’t know if it’s a car loan, let alone the exact make and model of the bloody thing.
And no, sorry, we have no way of knowing what their fucking “vertical” is, either, so we can’t display that. Fucking sales.
Asdhkjfsjfads
WHY MUST EVERYTHING SUCK7 -
Successful startup message on my friends discord bot:
Yo
His palms are sweaty, knees weak, arms are heavy
There's vomit on his sweater already, mom's spaghetti.
Bot Ready.
😂
https://github.com/nbd9/PastaBot -
When you can't figure out where you are supposed to add your code in the teams massive android spaghetti codebase. So you just add logs to every function that might be related to track down the function you need.
1 -
Writing bad code has its perks.
Whenever you are hungry you only have to write a few lines of code and you get some spaghetti3 -
The spaghetti monster is online.
Literally changes on the last minute.
Pushed to master, let CI/CD deal with it and left for lunch.
Bugs? Haha, sure.
Serious one? You can bet.
Do you care? Nope.5 -
Never heard of a so terribly designed online game.
For starters: the client-server model is process everything on the client, then save it on the server, and due to the nature of the site design, simply changing a tag will give you another of money.
The PayPal processing system doesn't read any headers or anything of that sort. So if you cancel your payment, this game thinks you've paid anyways.
Also, the trading system is based off of what buttons you can see so if you can see the cancel button it must be yours. So if you copy the cancel button to someones trade offering (FYI this is all done locally), and you click it you have gotten said item(s).
It gets worse, but I don't remember much more than that. The one thing they actually do is make session IDs expire.12 -
I have seen spaghetti php code, I have seen spaghetti JavaScript code, I have seen spaghetti python code. I have seen a lot of spaghetti.
Yet this Angular project appears like it was touched by His Noodly Appendage.
And only his Noodlyness knows what's going on in there. It's truly beyond my mere mortal means of understanding.3 -
Classmates having trouble with their mess of spaghetti code and improperly named variables (I saw variable names like "poop" already).6
-
Start a new job working in systems administration.
Create redundancy so you can finally pull out cables.
Trip over the fucking cables before you're able to impliment the switch.
....
Look for a new job
4 -
I get handed an API spec that has no naming convention followed for any of the JSON properties. Different for both GET and POST. I request fixes and get a "no budget" answer.
-
!rant
Four hours of work.
You think you write spaghetti code? I write spaghetti wires.
H-Bridge dual motor tester for stepper motors.
Speed is controled by pot.
H-bride are L293D.
My third board, and the first that won't go to the trash.
Question. With the baterry off the motor continues spinning with the 5v from arduino.
My question is, is the L293D suposed to do that? Or do I have a short circuit somewhere that is giving power to the motor? Meaning it can burn the arduino.
Runs a 12v stepper from a CD-Rom driver perfectly at 5v from the arduino and actually starts to act strange when I turn the 12v on. (maby the circuit it's adding 12v + 5v?)
24 -
Yes yes yes
Let's spend countless hours writing painful spaghetti that generates a financial report, extend that spaghetti for specs, then not bother to check the amounts or status. or where it says the money went. Nope, checking non-unique names is totally good enough. We're so good at this. Ten points to the legendaries.
Let's also make the object factories not create the objects correctly, and make sure that report includes entries for orders that don't include any actual payments. Oh, their status? "Ready to send" of course! Let's send that totally valid $0.00 to nobody!
Oh, but Root. Root, root, root. You can't ADD payments to this. no no no. if you do, it'll break specs everywhere else that uses that factory! Shame on you for suggesting it.
Pssh, now you want to make a payment just for this report? Why would you do that? Our best devs have been working on this for years! What could you possibly know that they don't? No, they're perfect. Don't touch them. Just make them better, okay? No take, only throw!5 -
When someone else's JS got you like... Want some meatballs and garlic bread with that spaghetti code?1
-
When you discover this new amazing programming language and play with it the whole weekend and then realize it’s Monday again and you need to go back to the office to work with some legacy GOTO spaghetti... 🍝🌧9
-
Almost 3 weeks back I joined a company as a React developer. For a week I had nothing to work on as they were already working on few projects.
So my senior asked me to take up a project(not yet live) which was developed by 2 interns, as the frontend guy's internship was about to end in 4 days I have to take over the front-end role.
So I talked to that guy for next 2 days regarding all the project scope, codebase and whatnot. But still not entirely convinced. As i got the repo access, I began to check the codes. God !! It was all spaghetti code. I was damn frustrated. And still I am.
This whole week I am trying to do the refactoring as much as I can, I completely lost interest.
I cannot blame the intern guy, he is smart and tried to do the best he could, as he didn't know about the company standards. Maybe I was too the same kind back then. Now he is gone and I am stuck building components over that code.
Bonus: He used some old react boilerplate.
-_-5 -
Starting a new project:
"I'm gonna write clean and commented CSS today"
===== 20 minutes in =====
"dafuq does this class do? "😣 -
I just spent 2 hours helping a fellow Sr Dev format an “if block” in code. Then helped show them how to step through the code. This is what passes as a senior at my company? I no joke have stayed at this job for 6 more months than I wanted to out of pure pity for my team. I want to quit so bad, but the team is in such terrible shape and can’t hire anyone new that is willing to stay. All good people personally, but gosh this job is just brain dead and eats my weekends when I should be focusing on family. Back to helping through the 500 line if block. There are worse things in life, but this just feels terrible.11
-
Anybody else know that horrible feeling when you're 2 weeks and 1000 lines of spaghetti into what started as a 2 day 200 line side project that was supposed to make your main project better, but has now become it's own life consuming beast?2
-
I like PHP.
It's not as bad as its reputation. Just because it's easy to learn, does not mean it's bad. In fact, with a framework like Laravel or Zend it's not so simple and keeps the whole spaghetti code developers away, which led to the bad reputation.9 -
That feeling when you're supposed to debug code someone else wrote a decade ago but it's such a horrible mess that your brain just gives up and you end up staring at your monitor for an hour in confusion 😵8
-
Fuckwit tried to lecture me on clean code.
Checked his work, it seems like he writes the spaghettiest spaghetti I've ever seen. Who would have guessed it. At least he knows that something called 'clean code' exists.5 -
Outsourcing front-end for web is like playing russian roulette, but with 6 bullets in 6 chambers.
You shoot yourself in the balls (or ovaries)... HARD.
I don't know how you can develop in a complete nightmare of a SCSS file - 3500 lines of insanity.
This dev must have changed his mousewheel at least 50 times!
SERIOUSLY, why the fuck use SCSS when you piss everything into one single fucking file???
What drives me completely nuts is the fact that he even used an @import to include his custom.scss file... how many more IQ poins are needed to realize that you could SPLIT your spaghetti into smaller, sane files?
I need a whiskey...3 -
Stacktraces with zero useful information.
Two full days of breakpoint stepping and framework spelunking.
"bifurcated" object creation.
Delegatd everything.
Inheritence hell fucking everywhere.
Models with both `has_one :x` AND `has_many :x`!?
Automatically-created objects when reading from magic virtual columns!?
What the fuck is this fucking four-dimensional spaghetti monstrosity and just how many angel puppies did I torture and maim in a previous life to deserve this nightmare?
And all of this to fix 12 fucking specs, out of the 1,780 this fucking ticket requires me to break and fix. FML5 -
My boss just passed me few tasks that my coworkers fucked up. They have more experience, but they do not follow any code style standards and usually write shitty spaghetti code. I'm pissed off and angry because it's not the first time and I'm tired of fixing things that they ruin. Do you ever had any situations like that? How do I handle this? I'm speaking of two particular persons, not a whole company.2
-
Account manager: "We somehow managed to take unmaintainable spaghetti code for money again. This is a great opportunity for you."3
-
I’ve become the person who I said I’d never be. Writing spaghetti code in spaghetti project instead of trying to refactor methods and classes where I’m adding new features.
Welp. They want it “yesterday” , they’ll have it yesterday.
But hey, the money’s good.8 -
TIL the term "Kangaroo Code" was also a popular sort-of synonym for "Spaghetti Code".
It more referred to languages that heavily used "goto"s (because it would be "code with a lot of jumps")10 -
Question time:
Has anyone used PHP unit with Selenium before?
I have a.. well words can’t explain it nice enough but, beyond a joke, not even funny, spaghetti code base I’ve come to inherit recently, which god help me, doesn’t follow any design patterns at all, it’s just a stamp this here, staple this down over here and throw paint at the wall and hope it sticks.
It’s a mixture of procedural and functional with the rare class kind of mess.
So attempting to refactor by any means is not a real possibility without some kind of behavioural testing in place first otherwise I know I’m going to end up breaking something somewhere and not even know it.
Also if anyone has had the privilege of such code bases, tips to dealing with the mess are appreciated.
Oh and no, I can’t rm -rf or start again.😭3 -
Tired of reading spaghetti code written by your team mates?
Sit right next to them and ask them to write unit tests for that code.
Smash their head on the keyboard everytime they have to think longer than 10 seconds on how to test a specific logic.
Strangle them with any wire you find nearby till they agree to break up that spaghetti code unless they already started within that 10 second time frame.
When the exercise ends, tell them this is what refactoring is and ask them to pass on the knowledge.5 -
So I joined this financial institution back in Nov. Selling themselves as looking for a developer to code micro-services for a Spring based project and deploying on Cloud. I packed my stuff, drove and moved to the big city 3500 km away. New start in life I thought!
Turns out that micro-services code is an old outdated 20 year old JBoss code, that was ported over to Spring 10 years ago, then let to rot and fester into a giant undocumented Spaghetti code. Microservices? Forget about that. And whats worse? This code is responsible for processing thousands of transactions every month and is currently deployed in PROD. Now its your responsibility and now you have to get new features complied on the damn thing. Whats even worse? They made 4 replicas of that project with different functionalities and now you're responsible for all. Ma'am, this project needs serious refactoring, if not a total redesign/build. Nope! Not doing this! Now go work at it.
It took me 2-3 months just to wrap my mind around this thing and implement some form of working unit tests. I have to work on all that code base by myself and deliver all by myself! naturally, I was delayed in my delivery but I finally managed to deliver.
Time for relief I thought! I wont be looking at this for a while. So they assign me the next project: Automate environment sync between PROD and QA server that is manually done so far. Easy beans right? And surely enough, the automation process is simple and straightforward...except it isnt! Why? Because I am not allowed access to the user Ids and 3rd party software used in the sync process. Database and Data WareHouse data manipulation part is same story too. I ask for access and I get denied over and over again. I try to think of workarounds and I managed to do two using jenkins pipeline and local scripts. But those processes that need 3rd party software access? I cannot do anything! How am I supposed to automate job schedule import on autosys when I DONT HAVE ACCESS!! But noo! I must think of plan B! There is no plan B! Rather than thinking of workarounds, how about getting your access privileges right and get it right the first time!!
They pay relatively well but damn, you will lose your sanity as a programmer.
God, oh god, please bless me with a better job soon so I can escape this programming hell hole.
I will never work in finance again. I don't recommend it, unless you're on the tail end of your career and you want something stable & don't give a damn about proper software engineering principles anymore.3 -
Shit recruiters say:
"We need solution experts, not language experts, because a language is just a tool."
Well then, good luck with your spaghetti code solution.3 -
Today I met the spaghetti man who wrote the code I work with.
Guess who's sharpening his knife (and d*ck)8 -
I came to this company. I saw spaghetti code. I told myself to write clean code and also clean the existing code. I took too much pressure for too little return. I am done with this shit. I will now write clean code but fuck the old spaghetti code!2
-
Who the hell thought that spaces OR tabs for indentation was an option?
For Spaghetti Monster's sake. An space is to separate words, one at a time. Tabs are for indents.
PERIOD
.28 -
In a month: I get married, I give a big project in college, I finish it (Master's thesis), I give a medium-sized project in a company and I play at a concert. I feel like I was mixed up in a big spaghetti pot xd7
-
I spent the last weeks rewriting a huge project which I had to hurriedly write a year ago. No comments, no documentation, spaghetti code. Part me was an asshole! But now I am done, all is new, everything is well commented, structured in classes with well defined tasks. Yay.2
-
when in doubt,
write everything manually,
because even if a package exists,
it's so old and outdated,
it's not even worth fixing all the errors,
so you may as well,
grow your own APIs
it'll be faster!3 -
1.5 million lines of undocumented spaghetti code. Think 500~1000 lines functions, 5k+ lines classes, string html concatenation. You name it, it had it. And complete unwillingness to improve it by the company. I eventually quit after considering doing it about 2, 3 times.4
-
Problem: ugly-ass php spaghetti code that has a technical debt of 16(!!!) years. I mean, it's so spaghetti that has two legacy frameworks that talk to each other inside the same monolith.
Observation: after two months my colleagues, trying to refactoring stuff, they were able to touch so little stuff that it almost made no difference.
How much is worth a rewrite? Because i don't think i can make a difference on a codebase so messy.
I know that rewrite is not the answer 99.9999% of the time, but i have tons of doubts here.13 -
I've pulled the third all-nighter in a row because of a ridiculous bug in legacy spaghetti..
I finally kicked its ass so I can now emerge from my cave, feeling like both a lifeless zombie and someone who got reanimated after half a week.
You all helped me through this tough time, love you all devRant ♥ -
Spaghetti Code, Spaghetti Code.
Flush it right down the commode,
Spins a call graph, unreadable size,
Anyone who sees it cries.
Look out, here comes the Spaghetti Code!
2 -
Boss: "how is the project going? When will you be finished? It's not that much to do right?"
Me - I'm stuck in my spaghetti. Not even started to implement things - fuck
3 -
For the past 45 days I've been the sole developer of a standalone Java application and doing some ops only, now I'm getting back to the spaghetti php bullshit they call code and for the past 5 minutes I could fell the depression striking back...
-
Client: Hey guys! Let us start a bunch of projects that are all dependent on each other and expect them to deliver those on time.
Me: WHAT. THE. ACTUAL. FUCK. -
Told by boss earlier that my job description should be changed.
It should be cook or chef, as I'm making spaghetti inside my editor.
He argued it could be risotto as well7 -
when you're at a job interview, the interviewer shows you some code to give you a taste and the first thing that comes to mind is, "how long is it gonna take to refactor and is it worth it..."
then proceeds on to show a database diagram and its an unholy cluttered spaghetti soup that even a purple octopus would feel a cold shiver from..
then the interviewer mentions the previous dev left suddenly and the deadline is very soon(TM?)..1 -
The codebase I'm currently working on is so fucking damn wrong that I made a folder for screenshots called "facepalm".2
-
The moment when you are too scared to make any needed changes in your code fearing you will untumble all the structured mess of spaghetti code you have written... 😳😨😕5
-
Hey guys, wanna see some spaghetti code? This is some parts of Yandere Simulator. More in comments
6 -
Currently rebuilding a web store backend originally developed in 5.2 and by an Indian guy who loved his spaghetti and his knowledge of version control is to do things like 'index.php, index1.php, index-old.php'. Even on the DB he does this... God damn9
-
developer: *deploying spaghetti code to production*
hacker: *alters the code with an injection*
developer:
2 -
Me: *joins devRant once again*
"Wow this community is surely active! Better check frequently to keep up!"
*checks two times in 6 hours*
"Yea it was weekend. Probs everyone is getting their hands in a dirty pile of compileable code or a spaghetti of jQuery."
So, how is your day/night so far?25 -
I love how clients can ignore missing menu in their existing project, pages not updating because of fucked up cache, having three different versions of jquery and half of the code being spaghetti on fire - but they get anally retentive about margins not looking like on the wireframes on the new project.7
-
In my short career, I've seen projects become legacy before their first release. Hell, I've seen proof-of-concept apps turn into technical debt because to management as long as it works we won't rewrite it.
-
I am 99% done with my academic project, but still the workload is heavy, and I've got too much on my plate already, mom's spaghetti
-
Me to my team:
Let's cook some rice this time. Instead of spaghetti. Grains would be separate from each other if we use the right ingredients.2 -
Sitting here looking at the shit spaghetti I wrote yesterday (that works) and wondering if it'd be easier to add more spaghetti for the feature I need to add or "do the right thing" and fix 1800 lines before I move on...4
-
!$rant
Well I feel accomplished today :) Got a lot done on my little devrant-widget project. I'm gonna try and make it open source soon, just trying to fix all this spaghetti code I created xD -
Database queries are slow.... quick add more indexes.
Tomorrow: Hey, why are database writes slow?
Rise. Lather. Repeat next week. 😡 Indexes can’t fix this spaghetti SQL!1 -
When you hack up some spaghetti code which works right off the bat and you don't even know why but you take it for granted anyways. Week later someone tells you that it's not working anymore and you have to find out why.3
-
I just realized one of today's emails is asking to review again that spaghetti program and this time figure out how to optimize performance because it is getting flagged for high cpu and database usage. A Niagra of If-statements and nobody-cares-for-comments-and-technical-documentation.
*bleep* *bleep* *bleep* previous programmer.
I'll deal with this torture on Monday.2 -
You know what's fucking horrible?
Implementing new features to an Android app in production that another dev wrote...
...which has no architecture, no documentation, no modularity, no testability, everything runs on the UI thread, filled with spaghetti code and it somehow works smoothely so I have to not fuck it up.
Oh and I'm also a junior. So fuck me, right?1 -
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 PROGRAMMER7 -
Slogging through half baked code, I wondered to myself... Who the fuck is Robert and where is he?
Quickly searching through Google and finding a handful of results I see that he had left long ago. Probably leaving for good reason. I'll never be able to ask him though. Never will I know why he left. He probably has a very sensible reason, but goddamn do I wish he left something that I could use to discern what he has created.
There is no documentation, no reasonable information about why anything was built the way it was, only just mountains of rusty ass baren code to scale down.5 -
There was a task of fixing up a payments page that features pretty complex logic. Initially it was like 200 lines of code, seems short but it was a fucking spaghetti mess. Never seen more cognitively complex code in my life.
So I delete the spaghetti and pull out the 500 lines fucking state machine. It works perfectly. It’s perfectly understandable even though it’s longer.
This is how I deal with problems. Shorter code isn’t always better code.4 -
I spent an hour to debug spaghetti trying to find out why this damn functionality doesn't work. Then I was told that close button actually saves your progress. I was always using close tab button in browser to close that page. Great UX GG
-
Oh great...
I am slowly beginning to realize that my boss/manager doesn't care about refactoring at all. He cares about features and resolved tickets and thats why the code is a pile of spaghetti filled with hacks to fit every clients desires.
Also all of my coworkers work for themselves, ticket by ticket, either because they just don't care or because they are so frustrated that they don't care anymore. And here I am, an intern, and they expect me to cope with this deformed clutter of legacy designs, buried under hacks and workarounds, while implementing some new feature which in the end I have to put on top of everything else because nothing of that codebase can be reused. Fucking shit, fucking irresponsible managers who dont think about the quality of their product. -
When your project partner is an absolute coding genius.
But writes spaghetti code with methods named function1, function2, ... function20.
How the fk am I supposed to read that code?!?!?!
But I’ll give him credit, the program is works and is amazing. It’s just not possible for anybody other than him to understand.7 -
To the 8 months ago *me*.
You're an idiot learn how to properly keep a changelog I just spent almost an hour fixig that freaking spaghetti mess you wrote!1 -
So, a spaghetti legacy code, written by some dude that obviously hates his job, needs update and we argue about spaces vs tabs....4
-
The project is nowhere near complete, the customers are waiting for demo/proof of concept. the code is spaghetti and I'm burned out.
Oh, and I'm a solo dev.2 -
Every now and then the front end guys try to slip in some backend code. When I notice it weeks/months later I start questioning my ability only to realise it was their shit hacks and not mine
-
Be me, get a consultant job, go to a supposedly great client that has fame of getting scouted by Google. (attn: I doubted all this shit before I started)
Learn the basics by a awesome mentor and trial/error stuff at the same time to get the hang of things, after that was done, I noticed there was no documentation whatsoever, code is spaghetti and your documentation, good luck!
Royal spaghetti, you can't make heads or tails of it, dev code in production, empty try/catch blocks, empty statements, if (true)... (incl. their core classes)
Keep in mind this is a multi milion dollar company...
Someone please understand my pain...6 -
It's funny how you start feeling bad for the next dev taking over your project because it turned into a total spaghetti code shit show that will be impossible to maintain in the future with new features coming in.
Honestly... if a projects starts out with a certain scope which then gets extended EVERY FUCKING WEEK with requirements that can't even be met in the initial timeframe it's no wonder the code quality will decrease over time.
This just reminds me daily how important good project management (and I'm not talking about suit wearing pain-in-the-ass-managers) and the inclusion of devs in the planning process really is.
It's so fucking crazy that companies run like that with people up front that have NO FUCKING CLUE what they are doing, nor do they understand the mechanics, tech and effort that go into certain features. They're like "beep, boop, it's done by Friday you fuck!".
The funniest part of this stupid charade is that the closer we get to a new "deadline" (we will not meet the deadline anyways) the more nervous the "managers" get. WHY didn't you properly plan this shit in the first place? WHY didn't you care for the last six months where all this fucking bullshit could still have been prevented?
Meanwhile I'm just so sick and tired of this shitty project and this sucky company that I just don't have any motivation left to keep on working. It's so fucking hard and painful to work on projects that suck ass, are poorly designed. I just got to the point where coding is no fun any more. Thank god I'm out of here soon... fml5 -
So I set up a raspberry pi to control my bedroom lights last year. I decided I wanted to add some more features to it and for the first time since I created it, started looking through the code I wrote.
First thing I noticed was the excessive amount of files I have. Like I get that I just wanted to throw this thing together as quick as I could but did I really need to create a file specifically for storing a 1 or 0 depending if the lights were last turned on or off for a startup check.
Secondly, I seem to have 2 index.html files for some reason.
And finally, the code itself is pure spaghetti. The website is running with a python script, which sends calls to a nodejs server, which executes additional python scripts to control the lights. No comments anywhere, and badly named variables are also a great combo.
And finally there is the occasional "Why the fuck isn't it working, fuck it I'll just unplug the pi and reboot it" that I have been dealing with lately.
Oh and don't forget that the log file is spammed by a debug message that is printed every minute.
God I feel so ashamed. I was proud of this until I looked at it just now.6 -
I envy all those developers with clean codebases and consistent coding standards and nice architecture.
I'm fixing bugs and optimize code in someone else written project. which looks like spaghetti. with naming conventions like "a", "bbb", "zA" comments written in unknown language and off course the deadline was yesterday.4 -
The one thing I've learned most about developers is that developers like their lasagna more than their spaghetti.3
-
I don't know why they made so many algorithms, data structures and big O questions during interview, when all they wanted me to do was to maintain some legacy, tight coupled, spaghetti code with no architecture, documentation, tests nor any kind of engineering behind :/1
-
90% of my time at work is spent debugging and fixing a horrible mess of years-old legacy spaghetti. The only "real" coding I do is my personal hobby projects at home.3
-
untangling some spaghetti deep in a tech-debt-ridden repo:
find the bug causing function
only comment:
`//TODO: replace this once <jira_ticket_url> is done`
go to url
updated: 3 years ago
I miss CS undergrad1 -
So third party devs that my employer hired to build our web based application used fucking spaghetti jQuery to validate all of it with no documentation. What a bunch of cunts.
-
I just styled something that appears to be an "parent" style change when a certain "child" was hovered.
Vanilla CSS. I think I've seen it all now.
My brain is spaghetti right now 🤪1 -
After 30 minutes of trying to figure out why a guid is empty, I realize it's because it is initialized, but not assigned.
I'm not ready for Monday. -
The object-oriented model makes it easy to build up programs by accretion. What this often means, in practice, is that it provides a structured way to write spaghetti code.
~Paul Graham -
Yea sure, I'd like to refactor your fucking 1000 loc spagetti code "module" with no documentation at all...3
-
I keep taking breaks from what I'm working on coming back and adding more spaghetti on top of the spaghetti because if I start rewriting the spaghetti I get in a cycle of rewriting spaghetti several times and getting nowhere
Why am I so indecisive =-=
But also I think I might have to rewrite the spaghetti again. Can my opinions stop changing pls7 -
Imagine a time when a colleague contributes a shitty spaghetti of non-optimized code that neither use mnemonic variables nor conventional naming of functions, and you can imagine the dark hours of maintaining it and your fingers itch to fix it but you don't have the time and the responsibility too to do it. He doesn't listen to you and you feel bad to tell this to the boss as the colleague is also a friend you've known since college and is a good person otherwise. No options seems to give peace.6
-
When you look back at your shit spaghetti code you only wrote 3 days ago, and you don't know whether to laugh or cry.😆😢1
-
10 years ago my bosses came to me: Make a few adjustments to the logic of this website. Should be a quick thing they said. Got a zip file later. Hundreds of php files. Inside, thousands of lines of the best PHP/HTML Spaghetti I've ever seen. No CSS though, but lots of nested table layouts. The best part: everything was in french, content, comments, varnames. The original dev didn't use includes for the most repetitive stuff, even db credentials were copied in every file. Took me a week.
Two weeks later: Change that and that please....
We decided to write everything from scratch then. -
I told you fucking moron clients doing that "little" change would be complicated and in the worst case it would end fucking up your whole spaghetti crap. A really HUGE spaghetti monster of that you aren't aware because you guys don't know a shit about coding conventions.
*Clients call me complaining about their software is broken*
-Hey, we're in serious trouble. Our users aren't being able to see the proper calculated values. Why that little change had so much side effects?
- I already told you why.
- Can you fix it asap? Our clients are complaining.
- No. Deploy an old copy of the affected modules while you give me a prudent time to refactorize that crap.
- Refactorize?
- ...
I used to work in their place, 3 years later I quit that crappy job and decided to make them my clients. I escaped from the micromanaging thing but I didn't from their ugly practices.
Anyways, I have to fix this shit asap. Money talks, at least until I can find a better client. -
Anyone remember my rant about Go and GTK? Well, the main problem was that it was 3 AM, I've since completed it, and have begun to refactor that spaghetti mess.
I feel so good right now.4 -
Somehow, a contractor left with all our unit tests six months ago. I just inherited this project. It's 200kloc of Django spaghetti, and I have no unit tests.5
-
I have a demo meeting tmr but the web app written by the junior dev is in crap state. Forget about new features and bug fixes, I probably won't even be able to correct and clear all the spaghetti codes. So instead of working on it, I am trying to encourage myself by creating quotes images.
-
After they look into your CV .. ask to look into their repo ! See what type of spaghetti they are cocking !10
-
Ugh I really wish I could just decide on something and role with it, haven't touched my book or website for a while so of course my websites code is all fucking horrible and spaghetti and I want to rewrite and revisit a lot of my book -,-
Why can't I just be happy with something like this! -
Who needs clarity and maintainability when you can have the adrenaline rush of debugging spaghetti code? 💻🦸♂️2
-
Another project, another team, another shitshow in codebase.
Now instead of doing work and implementing long awaited features... few weeks of minor refactorings ahead, untangling unnecessary complexities...
... but mostly - explaining the team why their 12-months work is pile of shitty spaghetti, and how it should really be done.
Explaining basics to "seniors" is the most exhausting thing.3 -
How can anyone justify the cofefing craploaded bullshitish error messages of bloddy java?
Who, in the name of the flying spaghetti monster came up with that brain damaged bitwaste?
Sorry if i offended brain damaged people with that comparison4 -
I just found the current main project of the people who originally wrote the codebase I’m mainly working with. After all these years they still write incoherent spaghetti mess. I need to make a throwaway GH account just to tell them people like them are the reason people hate PHP…1
-
Some Udemy courses are super cringe.
Can tell this guy isn't formally educated nor a professional programmer.
His code is so badly formatted and his naming conventions reeks of inexperience.
Spaghetti everywhere.4 -
How to tell to my boss that I waste more time using his code than rewriting my own? I don't want to offend him 😂1
-
So... I decided to refactor some of my old code that I wrote exactly 11 months ago, which was one month after starting work..
My first reaction was: "Was I so stupid?"
Second reaction: "why the fuck my supposed 'mentor' allowed me to write this bullshit?"3 -
What is easy to code at the moment isnt necessarily the best code in the long run.
- From the dev currently maintaining spaghetties of spaghetti code -
So today 1st April is the only date you can say mean things back to your coworker and say "April's Fool"
Eg. "Hey your code like spaghetti with sauce , go get ketchup, btw April's fool".18 -
Give me your legacy, your undocumented,
Your huddled classss yearning to be bug free,
The wretched security holes of your multiple backdoors.
Send these, the testless, spaghetti-code to me,
I lift my keyboard beside the golden door! -
Well, rarely gets updates (not as frequent as windows), and sure takes lot of time.
And I need to clean my screen with Ajax. After spilling some coffee and spaghetti.
6 -
Git should have an option - - gud which signs the last developer to commit to log each time it's called. (in case they borked it). That way, everyone could spam someone's stupid name who broke production.2
-
So a trainee made a website at the company where I also have my internship, he finished his internship earlier than I did. But the problem is I'm now fixing his site and it's literally falling apart! I fixed one problem and a dozen apear! His code is the definition of spaghetti code. It's so extremely bad I can't handle this, I don't want to do this anymore, just someone please drive a knife trough my chest. This is unbearable HE CREADED A HTML PAGE INSIDE ANOTHER ONE flipping heck how could you think that's how things work!1
-
Today I was forced to write spaghetti code.
When your database structure isn't set up properly, that happens...
I'm already sure I will need to revisit this piece of literal shit when we revise that structure. Though, it'll be much easier and logical, and I'll probably be able to just delete a big part of the code and implement it as intended. -
Spaghetti code
Mixing about 27 functionalities in an 800-lines-function accessing global variables.2 -
Does anyone here reject a requirement because there exists no elegant solution to it and you shall die before writing spaghetti code?🤔6
-
Android Notification in react !
i wanted to publish this a long time ago but i was super busy.
today i did it tho.
the code is still spaghetti !
https://nikandlv.github.io/react-mu...
6 -
I just became an android dev last week, yay for me. Though, I really hate how I inherited more than 50k lines of spaghetti!
They ask me to fix this and that, but that's okay for me, I can manage this.
The worst thing is we don't use any kind of version control system. And I'm always tasked to merge my work with other 2 android dev working on same spaghetti.1 -
Using the new project as an excuse to try out the language I was an absolute newbie at. (Python, at the time).
A couple years later when I’m much more proficient and I go back and look at that code, I want to slap past me for putting that spaghetti mess into production. -
When every related field has a god damn different way of working with the data on hand..
For example:
`tht_date` ("Y-m-d", Date) - expiration date on the product, hence, there can be multiple of the same products with a different THT
`tht_alert` ("-2 months", varchar, DateTime modify mutation string) - sending an alert when this interval is hit, and being the activator of the tht_date field (unless value is "none")
`tht_minimum` ("28", integer, quantity of days before tht_date) - to lock them from being sent out/collected.
...
How would you expect this ×not× to become a friggin' spaghetti when trying to resolve the best row ID?
These values are in the wrong spot in the first place, then they also act entirely different in relation to eachother..
I hate the person that set this up, for doing this. When is the madness going to stop...
FFS!! -
Fucking Django is the only project thaat claims to be for perfectionist but actually is a steaming pile of spaghetti code, data transfer objects, configuration objects and useless wrappers and shit. I mean this shits made by adults with computer science degrees how the fuck can they get that shit so wrong?16
-
Anything related to UIs or data science
That, working with a spaghetti codebase, or unhelpful and not nice teammates -
Love starting a brand new web project, knowing that you wont go down the same rabbit hole and spaghetti workarounds ‘cos the clients a dick scenario…. until of course you do. FML.1
-
Got accepted as a part-time FE developer in a well-known company.
Reality check: all I do is maintain a horribly formatted spaghetti code (20k+ lines in a file) using ancient tech like PL/SQL, prototypeJS and IE11.
Buy hey, at least I know some SQL magic now.. Right?!7 -
People in this discussion will refer to my classmates doing their project we were allowed to choose like 3 months ago and back then I already told them they won't ever manage to make it work in time.
People: "yo could you help real fast"
Me: "aaah not again but okay why not"
People: "here's the code"
Me: "the fuck is this? What is it supposed to do?"
People: "ummm it should doooo eeeerrr... Like this and .... Yeah we don't know. The output should look like that but it doesn't"
Me: "the fuck did you even try to do. That'll never work. And I told you the same thing like 3 months ago when you just chose the project. Just go and use some random math lib you find"
People: "kkkk"
Their code seriously made no sense at all. Parsing substring within like 5 nested loops and like 20vars called "s1" and "theString" and what not. -
Some days getting better at programming just feels like learning more sophisticated ways of writing up spaghetti
🍝 -
Six different .NET solutions using reflection to interface with each other just made OOP look a lot like spaghetti code.4
-
My first game jam,
I was first excited about coding but when I started, I was caring about making my code clean, and I lost too much time focusing on this... You should see the end, such a mess ! Spaghetti code, pointers everywhere but hey, it worked 😊 -
Got frustrated with trying to shoehorn an overly-customized, spaghetti code WooCommerce implementation back into one that is easier to maintain via plugins. Got on my bike and rode north toward my old neighborhood until I started recognizing landmarks. Part of me wants to keep riding and never return.
-
Solving leetcode problems for fun, as I’m highly interested in algorithm problems....and I go to the area where the discussion is, and this spaghetti is the first thing I see 😱
13 -
Jesus Christ, Minecraft source code (with forge in this case) is such a clusterfuck of spaghetti logic. It's especially fun when it uses a lot of reflection and dynamic class lookups...4
-
When there is no domain layer so the controllers are 2k+ lines of spaghetti, so after 5 months trying to fight iet you just give in and ask the gods of code for forgiveness1
-
A senior dev wrote spaghetti code containing business logic in the fucking controller with some code repeated in a couple of other places.
This is when a facepalm is not enough.1 -
Sigh.. KILL ME.. It's of those days.
Unfortunately I'm one of the few that has experience with PHP at the office. I'm asked to add some features to a website and it's custom CMS, both written by a designer. Spaghetticode here I come 😕😡1 -
Just learnt some new stuff today and I apologize to whoever is maintaining my spaghetti code.Just overhaul it buddy.
If it work don't touch it practice 🤠 -
Ever have one of those days where you work really hard on something only to be completely defeated by the architecture you're working in. I seriously want to rearchitect this entire damn project. Spaghetti code doesn't even begin to touch it.1
-
I've spent the last 3 days trying to figure out what on earth was going through the head of a (now departed) contractor when he wrote the code I'm trying to fix. Took a reasonably simple part of the system and convoluted it to the point where it makes no sense! And we've realised it's not complete either!! Fun times... they are not. 😕4
-
Magento Debugging Horror!
Changing lots of things in magento with no problem. Continuing development for quite sometime. Suddenly decide to clear cache to see affect of a change on a template in frontent. Suddenly magento crashes! There's no error message. No exception log. No log in any file anywhere on the disk. All that happens is that magento suddenly returns you to the home page!
Reverting all the changes to the template. Clear the cache. Nope! Still the same! Why? Because the problem has happened somewhere in your code. Magento just didn't face it, because it was using an older version of your code. How? Because magento 2 even caches code! Not the php opcache. Don't get me wrong. It has it's own cache for code, in a folder called generated. Now that you cleared all the caches including this folder, you just realized that, somewhere something is wrong. But there is no way for you to know where as there is absolutely no exception logged anywhere!
So you debug the code, from index.php, down to the deepest levels of hell. In a normal php code, once the exception happens, you should see the control jumps to an exception handler, there, you can see the exception object and its call stack in your debugger. But that's not the case with magento.
Your debugger suddenly jumps to a function named:
write_close();
That's all. No exception object. No call stack. No way to figure out why it failed. So you decide to debug into each and every step to figure out where it crashes. The way magento renders response to each request is that, it calls a plugin, which calls a plugin loop, which calls another plugin, which calls a list of plugins, which calls a plugin loop, which calls another plugin.....
And if in each step, just by accident, instead of step through, you use the step over command of your debugger, the crash happens suddenly and you end up with the same freaking write_close() function with no idea what went wrong and where the error happened! You spend a whole day, to figure out, that this is actually a bug in core of magento, they simply introduced after your recent update of magento core to the latest STABLE version!!! It was not your mistake. They ruined their own code for the thousandth of time. You just didn't notice it, because as I said, you didn't clear the `generated` folder, therefore using an older version of everything!
Now that after spending 7 hours figuring out what has failed with absolutely no standard way of debugging and within a spaghetti of GOTO commands (Magento calls them plugin), why not report it to github? So you report it with a pull request. This also takes 1 hour of your time. Just to next day get informed that your pull request is rejected because another person already fixed the bug and made the same pull request. It was just not on the latest stable version yet!
So you decide to avoid updating magento as much as possible. Because you know that the next Stable version will make your life and career unstable. But then the customer complains that the Admin Panel is warning him of using old Magento version which might pose SECURITY THREATS! -
Stupid shits, if I am converting this app from the VBA to a modern web app. Don't fucking suggest me copying and pasting tens of thousands of lines of shitty spaghetti code, into a new Web project.4
-
God, overhauling an entire application is tiring. Having to swim through mountains of spaghetti code is strenuous. I'm going to die before I ever finish >_<3
-
Nothing like trying to understand a single 1500-line source file that implements the API usage in the frontend. Without a single comment.
No, wait. There are comments! But it's only commented-out code. Or explicit shit (like "gets the version" before a getAssetVersion function).
Functions with unused parameters? ✅
Weird var names (like "tmpX")? ✅
`console.log(var)` everywhere? ✅
Long-ass lines with 150+ chars? ✅
Duplicate code? ✅✅
Not a single interface was used so everything is var: any? ✅
Random unreadable RegEx? ✅
If-chains of 6+ more levels? ✅
Many `else if` towers instead of a switch? ✅
And did I mention it was written by a fucker who can't speak proper English so shit like visiable, cataloge and isExist is everywhere? Yeah.
Fun day at the office reading spaghetti code 🙃 -
I just had to re-run some old scripts written in python, after a year and a half without using the language. Much spaghetti code, but strangely inebriating. 😯
-
Praise the Jesus/Allah/Buddha/Flying Spaghetti Monster, the newest Visual Studio Code version doesn't require reset after extension installation!1
-
'bout 8 hrs on trying to read spaghetti that uni-mates wrote for a project to create a drunkgame webapp. We had a good time but their code lacked meatballs 👨💻☕
-
When you feel that only you and maybe one other guy from the team care about product and do effort to actually refactor legacy spaghetti code while others just patch it up or even build changes on top of legacy spaghetti!2
-
somewhere in every spaghetti code there is a mysterious CTRL + C and CTRL + V that just can't explain itself2
-
You can be very good at writing algorithms and good quality code, but if your architecture is garbage, you'll be doing hacky fixes and end up with a spaghetti code.3
-
At my new organization , they love spaghetti code, they neither want me to refactor it, because it works. Special thanks to php.6
-
Disclaimer: the project I'm about to mention contains the first lines of Go I have ever written.
Still, I'm quite proud of how quickly I got it working considering it's also my first time working with GTK.
This project that I've been working on the past few days is finally done. But it's %50 percent spaghetti, so refactoring time. I decided to have a look at my cyclomatic complexity numbers, and my biggest function (not main()) had it at 7.
As it was quite large, I split it up into to parts: the preparation and the actual timer loop. As I appear to need to use a goroutine, by the time I'm done passing channels and all hell to handle them, my loop function now has a score of 9 for cyclomatic complexity.
So fix one bug, leaves two in its place?
But I still need to better learn Go, anyone have a good (relatively painless, informative, quick-ish) course they can recommend? I've been thinking of trying out codecademy's one...6 -
[Music]
-Do you like spaghetti?
-Yes I do, Yes I do.
-Do you like code?
-Yes I do, Yes I do.
-... Do you like... Spaghetti Code?
-No I don't, Yucky!
(Anyone with a toddler would get this)
(Honestly, I liked spaghetti code) -
FOR FUCKING FUCK SAKE
I have a shit ton work to do. Just finished (hopefully) all of my exams, came back to work and got tasked with simultaneously developing a new app (Android), adjusting some of my own code to work with client's specific requirements in completely different project (C#) and also I have to fix a legacy app (Android) because UE comitee will be visiting us on wendesday.
I've never seen this code earlier. I've never seen this WHOLE SHITTY PROJECT. Guy that was developing this left few years back.
It's a complete spaghetti. 550 FUCKING LINES OF CODE for a one class, most of the methods are deprecated and won't even try to work on Android > 4.0. No documentation. Nothing works. Whole code is ridden with bugs, warnings and looks like it's glued together with duct tape. I even had to migrate from fucking Maven to Gradle it's that old. -
Working with passed on spaghetti code.
Glaring at author's name.
Wherever you are.. I will find you.
And I will kill you. -
Last week I found this on some spaghetti code I was analyzing:
if (boolVar) {
...
}
if (!boolVar) {
...
}
if (boolVar) {
...
} -
i am so excited learning. now i'll start refactoring my plate of spaghetti into object portions. both are new topics to me.
-
During the last two weeks I have come to realize that I dislike holidays. Or maybe I don't, maybe it's just now that almost everyone is forced to use their holidays at the same time... anyway, I just know some junior has made a hot spaghetti mess that needs a'fixin and I don't look fwd to attending to those issues when I get back to the office... worst case the buggy spaghetti poo is already in prod1
-
Asked to map the old database into a diagram. Looks like someone threw up spaghetti. It is so full of tables named "obsolete" I don't understand!
-
When you play on lagacy shit spaghetti monster code with a fucking ass crack boss don't understand anything and bullshit you (yaya that code is perfect) !
I just want to drop that fucking job full of shit
Week 2 😂🤣😭 8 months come2 -
Just started rewatching Jurassic Park for the millionth time and can you imagine working with someone like Dennis Nedry? The messy workspace, spaghetti code, the only one with knowledge of completely obscure and complex code....hits a bit too close home1
-
Working with a spaghetti wordpress site makes me wanna scream. I don't even know if my changes have no effect because I fucked something up or there is some absurd caching system that thwarts everything I do.1
-
This moment when you pressed your "Auto-Indent" Hotkey and the whole software doesn't run anymore. Later you realize that it's because of your Auto-Indent and even worse - you realize you have to code on top of the spaghetti code...
-
Fixing a faulty plugin modification from a former developer, and no documentation, plugin provider wants payment for support...
Me crying on the side near to pull the trigger -
I wonder if there is any tool to measure the amount of spaghetti code in my project... it feels really messed up.
Anyone got a testing tool at hand for it?5 -
I do not like rust's choice to just infer something from how it is named
like if you install a package that begins with "cargo-something" then it becomes a cargo command. this feels janky
also turns out if you have a build.rs file it will build stuff for you when compiling? I just ran into this being described in the docs. well guess what. I have a build.rs file. it isn't being used for that though. I mean hasn't caused any problems, or has it?! I DON'T KNOW
config options seem more explicit than this naming nonsense. I just had to rename my project everywhere so it can be a cargo command. ffs now my git links are broken and shit.
I thought rust was verbose because it knew the merits of being explicit. can they stick to their principles pls8 -
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!4 -
For donkey, one can argue that WordPress is great, but for the developer, it really sucks. Customize it, feels like your soul tormented in eternal hell with its spaghetti code and unreadable variables.
-
I keep telling myself "I can do this, I can change this", but then I'm forced to write untested undesigned spaghetti code cause we need another hotfix for 3 hours from now...
-
Anyone else have the new MacBook pro, and feel like they are working off of the flying spaghetti monster?1
-
I am in a slump. I keep writing spaghetti code. Is there any platform where I can practice Object Oriented principles?1
-
Can't believe I miss my old job. Pay more here but works so much more it's crazy, and issues just never die, pages keep happening, too many clients calling our APIs and everything is spaghetti. I don't think my manager will ever promote my as it's tough to perform tbh (atleast for me).
-
The worst thing ever is freaking NS datatypes, who thought that was a good idea? My code looked fine and worked fine till you made it spaghetti, thanks apple
-
Have you already met the code that you have no idea how to refactor?
In five years I met those twice and I'm still puzzled with one of them. (I don't mean just a spaghetti or too long code) -
Botched the technical interview with the CTO he got me with fucking left joins x,) I'm forever stuck at my dead end job, I'm destined to wither in that wilderness of spaghetti and poor practices2
-
When I get a code review by my self-proclaimed expert colleague suggesting a change that ends up breaking the feature, I just implement that spaghetti code and let the testers know I'm not to blame.
-
Documentation. I know what I'm doing here. Future me will have no idea though. Neither will the suckers who have to maintain this spaghetti
-
Starts new codebase
uses boilerplate with the intent to keep a clean structure.
after 2 weeks it already a complete bunch of spaghetti code and doing things like putting the same image in 4 different directories... boy i wonder why i could never hold down a job as employee...2 -
I lose interest in my job whenever someone goes into my perfectly decoupled code and adds spaghetti code into it to make things just work for them. Sigh...when will people understand and learn to write maintainable software...
-
Wrapping applications is PITA. It would be cool and all, but the app outputs debug(ish) messages into stderr, which just makes me write more spaghetti :'(
Top Tags
Weekly Rant
View