Heard a conversation between my colleague and the boss

Boss: (saw my colleague's messy desk) hey, could you organize your desk? It's not nice to see when clients come in. You know what they say, messy desk represents a messy brain..

Colleague: (glanced over to the boss' empty desk) and what does an empty desk say for the brain?

Am I the only one that uses chopsticks to eat snacks at the computer?!?

"Let's do some pair programming! It will be fun!"

... Fuck no.

Either I start coding and you open a beer, or the other way around. And sure, I do not mind doing each other's code reviews. I respect your feedback.

But I can't look over your shoulder while you misspell keywords. When I write code, I search, try, debug and play at a high speed.

I'm an impressionist/surrealist writing messy passionate functions, breaking lots of things with broad paintbrush strokes before finishing it into detailed perfection. I remember all the places in the code I need to work on, and cover everything with tests.

You're a baroque coder, sometimes even a hyperrealist, with your two-finger 10 wpm typing, writing code strictly line-by-line, decorating every statement with the right checks & typehints in advance. You can not keep two functions in your head at the same time. You write tests reluctantly, but you hate that I barely plan. You plan everything, including your pee breaks.

As a coworker I respect you.

But there is no bigger hell than pair programming with you.

My home setup is always messy... So, I’m posting my office setup...

First off I dont mind what OS you are using. This rant isnt about the OS but about hypocrisy for some of the users. Secondly Im sorry for typos, I typed it on my phone while waking up.

People are calling Windows spyware, so they are using Linux or MacOS. Even though I disagree with the term spyware I would be fine with that if you weren't a hypocrite.

How many of the people who use Linux and call windows spyware uses Google, Apple, Facebook or Twitter once in a while? I highly doubt you if you say you don't.

A few years back Ive tried to live without anything of google, this also meant blocking YouTube, their trackers an javascript libraries.
Not much of the internet still works if you block google servers.
Google is everywhere and always collects data.

Facebook and twitter also collects data about you. Everyone who has your number in their phone will share it with Whatsapp and google so they can build up a profile. Even if you dont block it.

What I am telling you is that its impossible to avoid being tracked by these companies (including MS).

Every company I mentioned here has a profile on you, if you want it or not.

So let's check which of these companies tries to follow European laws.
Google gets fine after fine but doesnt really try to avoid it.
It looks like Apple, MS, Facebook and Twitter are doing it better on this.

But if you check the European law every European citizen is allowed to request their complete profile collected by a company. And that means complete and not the public part you volunteered to give away.

So I tried it out.
Google didnt want to give it, apple didnt want to give it, Facebook didnt want to give it and Twitter doesnt want to give it.

The hypocrisy is becoming clesr with the following. I did get my complete profile from MS. It was a messy PDF file which crashed most PDF readers.
It contained a list of people I know and how I know them. It contained MS accounts I had in the past and my hobbies. (and quite a lot more)

So from these big companies MS is the only one following the European Law.

So yes they do collect data, but they are open in what they collect.

And Im not saying here that Microsoft is great just because they follow the law.

You can have your own opinion about this and do with it what you want. I just wanted to share some, maybe alternative, facts.

And again this isn't an OS rant or whatever. I dont mind what you do, but I do mind hypocrisy.

I fucking hate CNET already. I mean who likes a website which autoplays a video everytime you visit them, with 200% volume.

But this time, I am just so fucking annoyed. Here is the title of an article:

"iPhone 8, X's wireless charging is a game changer for Android"

And the subtitle:

"When it comes to Apple, plenty of Android phone makers are monkey see, monkey do."

FUck you motherfucker. "Monkey see, monkey do". Are you fucking kidding me you cunt?

Remeber your 3D touch bullshit? Your fucking wireless charging will be bullshit too.

"the rest of the phone users make do with messy cables."

Maybe you're a fucking imbecile who doesn't know how to manage simple cables and ends up with broken wires.

You know who looks like a monkey? Some apple users who uses that shitty looking wireless earphone, which looks like monkey's dick you asshole.

Fuck off!

I. FUCKING. HATE. MOBILE. DEVELOPMENT.

I already manage the data, devops, infra, and most of the backend dev.

We had a mobile guy. He was great. I never had to think about it and kept moving quickly on my work. #SpecializationOfLaborFTW

He left. Why? Because they wouldn't give him a small raise despite being one of the best mobile engineers in the firm. WTF.

I made the mistake of picking up just enough slack on this workflow in the interim such that I'm, apparently, the fucking god-damned release manager, fixer of pipelines, fixer of build configs, fixer of anything where someone just needs to RTFM for a half-hour to not fucking break things.

Now, 8 months later...and, apparently, Fortune 500 companies are too fucking god-damned cheap to pay for someone who actually knows WTF they're doing for a very reasonable thing to have at least one dedicated set of eyes for.

I never wanted to be a mobile dev.
I never will want to be a mobile dev.
And I certainly don't want to manage your HALF-FACE-FUCKED detached expo configs.

There's a reason I never intentionally involved myself in mobile. All the way down, it's just shitty cross-compilation, transpilation, dependency-hell, brittle-as-fuck build processes so we can foot-gun and mouth-gun react-native and expo and babel and whatever the fuck else cargo-culted horseshit into the wild.

And why? What's the actual fucking root cause? The biggest white elephant that ever fucking elephant-ed? It's because Apple and Google decided to never collaborate on a truly-native cross-platform SDK--where engineers could write native code that compiles to native binaries that's simply write-once, run-everywhere. They know they could have done that, and they didn't. So what'd they get back? Expo--a too-cleverly-designed backdoor/hack--more-or-less a way to circumvent the sane release process software has usually followed: code -> executable -> deploy. Or code -> deploy (for interpreted langs). Expo's like "keep your same executable, we're just gonna to do updates by injecting new code into it whenever we want". Didn't we learn anything with web? Shit gets messy real quick? Not to mention: HEY EXPO, WE WERE ALREADY BUILDING NATIVE APPS, YOU SHORT-SIGHTED FUCKS. THANKS FOR LURING OUR CTOs INTO FORCING EXPO DOWN OUR THROATS W/ THE IMPLICIT (BUT INCORRECT) TOO-GOOD-TO-BE-TRUE PROMISE THAT WE CAN HAVE WRITE-ONCE, RUN-ANYWHERE WITHOUT ANY BUY-IN OR COOPERATION FROM THE ACTUAL TARGET PLATFORMS.

And, we just, like, accept this? We all know it's garbage engineering. The principles we learned in the classroom aren't just academic abstractions--they actually yield real-world results--and eschewing them yields real-world failures. Expo is tightly-coupled to high-heaven, with leaky abstractions six-ways-to-christmas, chock-full of foot-guns, and fails the most basic test of quality: does it, "just work?"

Expo is fucking shameful and it should fucking die. Its promises are too bold, its land-mines too many, its future-proof-ness is alway, always, always questionable as fuck and a risk to every project that uses it.

You want a rant? This is my fucking venue, 'tis not? Well, then this is a piss and vinegar rant straight from my blood-red, beating fucking heart:

EXPO FUCKING SUCKS. AND IF YOU'RE A FAN, YOU FUCKING SUCK TOO.

Me and small projects:

*writes messy but functional code*

*leaves code for a week*

*wants to finish code*

*code too messy - starts from scratch*

*leaves code for a week*

*wants to finish code*

*code too messy....*

Found this during my vacation. That poor bastard

Searched stackoverflow and found the exact issue I was having. The question is from 2014.

The accepted answer is a messy hack. Fuck.

The second answer is clean, clear, concise. It was posted 38 minutes ago.

Is this real life?

Will you PLEASE stop just commenting out code that doesn't work
Delete it
Please

Every day.

I am a PHP developer.

Yeah, "another PHP is awful" rant... no, not really.

It's just unsuitable for some ambitious projects, just like Ruby and Python are.

First of all, DO NOT EVER use Laravel for large enterprise applications. The same goes for RoR, Django, and other ActiveRecord MVCs.

They are all neat frameworks for writing a todo app, as a better-than-wordpress flexible blogging solution, even as a custom webshop.

Beyond 50k daily users, Active Record becomes hell due to it's lazy fat querying habits. At more than a million users... *depressed sigh*.

PHP is also completely unsuitable for projects beyond 5M lines of code in my opinion. At more than 25M lines... *another depressed sigh*.

You can let your devs read Clean Code and books about architecture patterns, you can teach them about SOLID & DRY, you can write thousands of tests... it doesn't matter.

PHP is scaffolding, it's made of bamboo and rope. It's not brick or concrete. You can build quickly, but it only scales up to a certain point before it breaks in multiple places.

Eventually you run into patterns where even 100% test coverage still doesn't guarantee shit, because the real-life edge cases are just too complex and numerous.

When you're working on a multi-party invoicing system with adapters for various tax codes, or an availability/planning system working across timezones, or systems which implement geographical routefinding coupled to traffic, event & weather prediction...

PHP, Python, Ruby, etc are just missing types.

Every day I run into bugs which could have been prevented if you could use ADTs in a generic way in PHP. PHP7 has pretty good typehints, and they prevent a lot of messy behavior, but they aren't composable. There is no way to tell PHP "this method accepts a Collection of Users", or "this methods returns maybe either an Apple or a Pear, and I want to force the caller to handle both Apple/Pear and null".

Well, you could do that, but it requires a lot of custom classes and trickery, and you have to rewrite the same logic if you want to typehint a "Collection of Departments" instead of "Collection of Users" -- i.e., it's not composable.

Probably the biggest issue is that languages with a (mostly) structural type system (Haskell, Rust, even C#/JVM languages to some degree, etc) are much slower to develop in for the "startup" era of a project, so you grab a weak, quick prototyping language to get started.

Then, when you reach a more grown up phase, you wish you had a better type system at your disposal...

All those fingerprints... I am TRIGGERED. It's like he stuck his fingers into a philly cheese steak and then smeared them all over the screen.

In my college days i was designing a bootloader for avr microcontroller , i had the idea to flash code wirelessly to avr over bluetooth and also cross compile the compiler for android device so that you can code on android, every thing went well just one thing didn't, i saw that code of certain size is executing properly , greater than that size gives me wired outputs so i have to dump hex from the avr (that is flashed the by bootloader) and compaire it with the original hex of code it got messy as you can see, most fun part of this bug is that error can be anywhere cross compiler may be fucked up , the bootloader may be fucked up , or it may be my bluetooth module , after 14 hours of staring at the hex code i figured out the mess in bootloader instruction that was changing the page address for flashing .

when it worked it was 3am in night i literally burst into tears of joy next day bought myself a cake to celebrate

I started a nee personal project few weeks ago. I named it SelfVPN. Its simply a VPN client that lets you create DigitalOcean droplets and install vpn server without opening DigitalOcean panel. You just need to add your api key in application.

It takes like 5 min to create new server and deploy vpn server. So I am paying hourly usage of vpn! Even if I don't destroy droplet it wont cost more than 5$ a month.

I am thinking to open source it. But code is too messy 😅 Here is the first look of it

Guy from work: "I have a messy coding style ¯\_(ツ)_/¯".

No, you have a bad coding style. Your repetitive uncommented spaghetti code isn't an artistic expression of your quick imaginative mind jumping from thought to thought. It's a horrible mess that shows me that either you can't do any better or you don't care.

*creates a freelancer account on some website.
*builds portfolio and gets things running.
*meets his first client.

Client: Hello. so your profile says you are an experienced full stack developer. You are just the kind of person i've been looking for.

Me: Yep.

Client: Okay I have a project for you. I am looking at developing a simple website that has a few functions and the budget is 100$.

Me: Okay smooth. Hit me with the descriptions.

Client: it's going to be a dating website. Once a user signs up; the website would automatically take control of the user's media devices in his/her home; automatically playing something romantic. You get me?

Me: Em... Idk about that it seems a bit...

Client: it can be done! Develop the algorithm.

Me: Em... Ok.

Client: Well, next the website uses some complex sorting algorithm and sorts existing members based on their past real life relationships. It puts the best people above the messy ones.

Me: o.0

*client goes on with his bullshit in like another 10 lines of messages.

Me: -_-

Client: so what do you think? How soon can you begin and how soon can we be done?

Me: Do you also want a "butt scratcher" feature? Like a hand pops out of the monitor and asks to scratch the user's anus?

*client leaves the chat.

Me: Oh. I guess he a thing against family guy.

PHP sucks balls,
It takes forever to do anything, it is so messy it feels like walking through a massive pile of shit!

Ok good I have your attention and that ++ 😇

But no this is not that kind of rant, quite the opposite.

In 70 lines of php shit as some people would call it, I am currently scrapping GitHub pages with ebook collections and with some minor regex pulling PDFs out and saving them to file.

Had a meeting with my boss earlier. Got yelled at for:
a) Working on a high-priority, externally-committed ticket (digit separators) that i was 85% done with on the Friday afternoon before my vacation instead of jumping to a lower-priority screwdriver ticket that just came in. Even though my boss agreed with me that what I did was exactly what I should have done, it's still bad because I was apparently rude to product by not doing as they asked?
b) Taking too long on that digit separator ticket that amounts to following a gigantic mess of convoluted spaghetti and making a few small changes, and making sure it doesn't break the world because it's all so fucking convoluted and fragile as hell. Let's not even mention my 4-10 hours of mandatory useless meetings every week.
c) Missing something that wasn't even listed in that same ticket -- somehow my fault? -- so I very obviously didn't test my work. Even though specs all passed and QA also tested and signed off on it as working and complete. Clearly half-assed and untested. Product keeps promising/planning UATs and then skipping them, and then has the audacity to complain about it.
d) Not recovering fast enough from burnout and daily mental breakdowns. I can still barely get out of bed and you want me to be super productive? Got it. Guess what? I'm being amazingly productive for my mental health. But my boss, Mr. Happy-go-lucky, thinks depression is dropping your icecream cone on your clean kitchen table, and this three-ton pile of spaghetti is "maybe a little messy, I guess."

So I need to somehow "regain the confidence" of both him and product because I'm taking awhile on difficult tickets (surprise), while having these ridiculous breakdowns (surprise), and because I don't fix things that aren't even listed in the fucking tickets (fucking surprise) -- and worse, that the lack of information is somehow entirely. my. fault. (surprise fucking surprise)

GOD I HATE THESE PEOPLE.

My little cellar room 🤗
(Usually much more messy than that, just cleaned up a bit for the photo)

Today is a sad day.
A sad day indeed.
I used to live with my parents for pretty much my whole life until the beginning of this year, when I decided to move and starter living with a friend, in his apartment.
By far, one of the things that I've missed most from my parents' house was the dogs. Boy, I love those four pretty little creatures.
Being a fulltime developer in an area that I honestly don't like that much, I really appreciate my after-work hours. Specially because of the time I could spend with the dogs.
So, the first months away were quite hard. Even though I was living with a friend, I couldn't help but feel alone and really depressed at times.
But then, my friend and my girlfriend decided that it was a nice idea to give me something to grow with again. And Jolyne, my beautiful, smart and messy little dog came to the apartment.
Boy oh boy, my bright days were back.
Getting home and seeing those four small legs and a shaking tail running on my direction was everything I could ask for. I was happy again.

Fast-forward to today.
I finally finished the code for a project I was working on. Everything was working fine. A good day indeed, good sir. Have one on me. - then my friend called me, which is weird considering we almost only talk through Telegram during the day.
All he had to say, with a sad voice and painful tone, was "man... I don't know how to tell you this... But Jolyne is dead".

And that was it. Every good feeling I had was now dead. And a part of me as well.
I stood there, speechless. I mean, I just couldn't believe what I've just heard. She was happy by the morning. We were playing before I left for work. Everything was fine.
Then, four hours later, it wasn't. She was gone.
I came home to a friend that didn't have any more tears to shed. And no dog came running to me like usual.
My fluffy little friend was laying on her bed, like she was sleeping normally. Like nothing had happened at all. She was just sleeping and have not noticed me... At least that was what I wanted to believe.
Three hours had passed then... And I just can't fathom the fact that my dog won't be here anymore. That I won't be able to play with her again like I do every night. That I won't listen to her running around with her toys. That I won't be able to hug her anymore.

I still don't know what to do. I mean, she will be buried. I've already arranged everything.
But I don't know what to do about myself. I don't know how to deal with this pain I'm feeling.
But I will try to move on... I just don't know how.

I'm deeply sorry for bringing you this story. For just writing it down here, like you guys need to share my pain...
But I needed to write this down somewhere. And this place is pretty much the only one where I feel comfortable and welcome enough to do this.
Thank you for your time, my friends.
Thank you.

We have a new developer working in our office. He is fairly new, which is understandable, so he asks for help regularly(which I actually appreciate). This time however, he asked for help, and every step of the way argued it. He said he needed help making a small circle(it's just an indicator on a table).

I told him if there is a mat-icon it would be simple, but if not it would still be pretty simple with CSS. He argued that those two options seem messy. I pointed out they are extremely clean actually, and showed him how it was only about 4 lines of css. and 1 if there was a material icon. He agreed it was pretty easy, and then went with a complicated way to have green or red. I let him know that was really trivial, and even gave him the exact code he needed for it(at this point, he could have copy and pasted, adjusted the conditional to the name of his variable, and be done).

He proceeds to take 3 more days to complete this task, making a new component for a colored circle, using templates and nested css in the html, and hard coding the color as opposed to using the material colors we use site wide. All in all 100+ lines of code. And he felt my solution with fewer than 10 lines was messy.

Being one of the top devs (and a good student admired by most lecturers) at college, my most humbling experience was when I joined my first job. I thought I knew SQL, I thought I knew C#. I realized in the first week, the thing I didn't know was "I don't know jack".
Thanks to a couple of great mentors (it took a few of them to bring me up to speed :P), I learned that the more I learn something, the more I will realize how much more there is to learn. I used tools to create storyboard animations in WPF, and my mentor would write it all in XAML! I'd write messy SQL and the other mentor just reduces it to a couple of elegant lines. They were like tech gods to my college self, all while being humble and friendly.
They also imbibed in me a sense of responsibility to carry on the culture of mentoring my juniors, which taught me much more than just the technical side of our profession.

I know a guy, about 50 years old. He is a self-taught programmer since he was young, and he has always used Visual Basic (never anything newer than VB6).

He once needed to interface with a web application I wrote, so I asked him to send me a POST HTTP request. He didn't know what I was talking about. No notion of REST, sockets, HTTP, nothing.

The he showed me his code. Actually, his codes. He had multiple copies of the project, one for each version, and he even kept multiple variations of the software in different separate folders. He probably doesn't know what "version control" even means.
You think this is messy. You didn't see the actual code (it's a huge application!).

Spaghetti all over the place. Meaningful variable names, what are they? Default names for the controls, like button1, button2, etc, with forms with more than 30 buttons and text fields. This was the most incomprensibile code I have ever seen.

You might think that this guy is just a hobbyist.
No.
He sells his applications. To companies. They are obviously full of errors, but they buy them.

Now, if you're still with me, two questions come into my mind:

- why?? I hate this, because it's impossible to prove to a non-technical person that this is *not* software development.
- how do I know that, to someone else, I am not like him? How can I be sure that I know and will know what needs to be known?

A bit messy atm, but I am an EE as well as a developer, so I like to build the things I program ^_^

When you see a semi bald man with a messy beard, bit too much belly, a dead look in the eyes that carries a pc bag.

And your first thought is "oh, a sys admin" x)

aslkfjasf. i've spent 12 hours today (and lots more over the past two days) trying to reproduce a bug that my [sort of] coworker insists is present. I haven't seen any proof of it anywhere, let alone steps to reproduce it.

I've poured through the code, following all of its tangled noodles of madness from start to fuck-this-shit. I've read and reread the pile of demon excrement so many times i can still read the code when i close my eyes. so. not. kidding.

anyway, the coworker person is getting mad because i haven't fixed the bug after days, and haven't even reproduced it yet. This feature is already taking way too fucking long so I totally don't blame him. but urghh it's like trying to unwind a string someone tied into a tight little ball of knots because they were bored.

but i just figured out why I haven't been able to reproduce it.

the stupid fucking unreliable dipshit ex-"i'm a rockstar and my code rocks"-CTO buffoon (aka API Guy, aka the `a=b if a!=b`loody pointless waste of mixed spaces and tabs) that wrote the original APIs ... 'kay, i need to stop for breath.

The dumbfuck wrote the APIs (which I based the new ones on mostly wholesale because wtf messy?), but he never implemented a very fucking important feature for a specific merchant type. It works for literally every type except the (soon-to-be) most common one. and it just so happens that i need that very specific feature to reproduce this bug.

Why is that one specific merchant type handled so differently? No fucking idea.

But exactly how they're handled differently is why I'm so fking pissed off. It's his error checking. (Some) of his functions return different object types (hash, database object, string, nullable bool, ...) depending on what happened. like, when creating a new gift, it (eventually...) either returns a new Gift object or a string error basically saying "ahhh everything's broken again!" -- which is never displayed, compared against, or recorded anywhere, ofc. Here, the API expects a Hash. That particular function call *always* returns a Hash, no matter what happens in the myriad, twisting, and interwoven branches the code could take. So the check is completely pointless.

EXCEPT. if an object associated with another object associated with the passed object (yep) has a type of 8. in which case, one of the methods in the chain returns a PrintQueue that gets passed back up the call stack. implicitly, and nested three levels in. ofc.

And if the API doesn't get its precious Hash, it exclaims that the merchant itself is broken, and tells the user to contact support. despite, you know, the PrintQueue showing that everything worked perfectly. In fact, that merchant's printer will be happily printing away in the background.

All because type checking is this guy's preferred method of detecting errors. (Raise? what's that? OOP? Nah, let's do diverging splintered-monolithic with some Ruby objects thrown in.)

just.
what the crap.

people should keep their mental diarrhea away from their keyboards.

Anyway. the summary of this long-winded, exhaustion-fueled tirade is that our second-most-loved feature doesn't work on our second-most-common merchant type.

and ofc that was the type of merchant i've been testing on. for days. while having both a [semi] coworker and my boss growing increasingly angry at me for my lack of progress.

It's also a huge feature, and the boss doesn't understand that. (can't or won't, idk)

So.
yep.
that's been my week.

...... WHAT A FUCKING BUFFOON!

Boss comes in and gives me some js code for syncing data (he hacked it together the other day, really messy with like 5 callback lamdas stacked into each other)

Boss: Make it faster and more reliable and add some progress indicator

So i look at the code and he literally pulls all the data as one json (20+ MiB). Server needs multiple minutes to generate the response (lots of querys), sometimes even causing timeouts....

So i do what everyone would do and clean up the code, split the request into multiple ones, only fetching the necessary data and send the code back to my boss.

He comes in and asks me what all this complexity is about. And why i need 5 functions to do what he did in one. (He didn't -.-). He says he only told me to "make it faster and show progress" not "to split everything up".
So I ask him how he wants to do this over HTTP with just one request...
His response: "I don't care make it work!".

Sometimes i hate my job -.-

Last week, someone contacted me, he said he needed me to fix the existing code on a new WordPress website because the developer did a messy job, so I thought to myself, it can't be that bad, requested for the SSH access and got into the server.

Guys.

Guys..

Guys...

I was wrong, some people really know how to fuck shit up.

I don't want to go into details but there were legit more than 50 plugins installed and activated on the website for no good reason and all the pages took about 45 minutes each to render if not more, so you can literally request a new page, start making coffee and use the washing machine and if you are lucky to have spent 45 minutes, return to a fully loaded page.

For a new WordPress website, it seemed really old.

It was almost as if this developer had a line of code that looked like this:

@Import 'all the bad programming practices ever and the ones yet to be invented';

This codebase reminds me of a large, rotting, barely-alive dromedary. Parts of it function quite well, but large swaths of it are necrotic, foul-smelling, and even rotted away. Were it healthy, it would still exude a terrible stench, and its temperament would easily match: If you managed to get near enough, it would spit and try to bite you.

Swaths of code are commented out -- entire classes simply don't exist anymore, and the ghosts of several-year-old methods still linger. Despite this, large and deprecated (yet uncommented) sections of the application depend on those undefined classes/methods. Navigating the codebase is akin to walking through a minefield: if you reference the wrong method on the wrong object... fatal exception. And being very new to this project, I have no idea what's live and what isn't.

The naming scheme doesn't help, either: it's impossible to know what's still functional without asking because nothing's marked. Instead, I've been working backwards from multiple points to try to find code paths between objects/events. I'm rarely successful.

Not only can I not tell what's live code and what's interactive death, the code itself is messy and awful. Don't get me wrong: it's solid. There's virtually no way to break it. But trying to understand it ... I feel like I'm looking at a huge, sprawling MC Escher landscape through a microscope. (No exaggeration: a magnifying glass would show a larger view that included paradoxes / dubious structures, and these are not readily apparent to me.)

It's also rife with bad practices. Terrible naming choices consisting of arbitrarily-placed acronyms, bad word choices, and simply inconsistent naming (hash vs hsh vs hs vs h). The indentation is a mix of spaces and tabs. There's magic numbers galore, and variable re-use -- not just local scope, but public methods on objects as well. I've also seen countless assignments within conditionals, and these are apparently intentional! The reasoning: to ensure the code only runs with non-falsey values. While that would indeed work, an early return/next is much clearer, and reduces indentation. It's just. reading through this makes me cringe or literally throw my hands up in frustration and exasperation.

Honestly though, I know why the code is so terrible, and I understand:

The architect/sole dev was new to coding -- I have 5-7 times his current experience -- and the project scope expanded significantly and extremely quickly, and also broke all of its foundation rules. Non-developers also dictated architecture, creating further mess. It's the stuff of nightmares. Looking at what he was able to accomplish, though, I'm impressed. Horrified at the details, but impressed with the whole.

This project is the epitome of "I wrote it quickly and just made it work."

Fortunately, he and I both agree that a rewrite is in order. but at 76k lines (without styling or configuration), it's quite the undertaking.

------

Amusing: after running the codebase through `wc`, it apparently sums to half the word count of "War and Peace"

I hate all of these rants about JavaScript being a terrible language.

In reality, it's one of the easiest languages to work with. This makes it easier for new programmers to write messy code, but is it the language's fault?

People get mad about the things that happen when you multiply "undefined" and a string...what do you expect?

You also have the freedom to choose from a variety of tools the community has created to solve existing problems. People just don't realize that they don't *have* to learn everything, you just learn as you need them.

Don't blame JavaScript for you bad programming, terrible type conversion needs, and great tooling.

Normally I just read rants but my new assignments is just to much and I have to vent a bit.

So I was assigned on a new company to help them with their automated tests (I'm normally a developer) which was fine for me. Especially when they said a guy that have 10+ years of experience have worked on the framework for a couple of weeks so it should be fine and ready. So I though it would be a quick deal.

But then I got there and... it's the worst C# code I have ever seen. I can live with the overuse of static, long method and classes and overally messy classes that doesn't really seems to fit (it's bad but not unusual in test code it seems). My biggest problem is overuse of the damn "dynamic" keyword.

Don't get me wrong, dynamic can be good and it have it's uses but here they use "dynamic args" in every single method, every one! They don't care if the method only require one value or ten values, they use dynamic args. Then you follow this "dynamic args" parameter going in to sub method after sub method and you have no idea what they use.

And of course they don't know if anyone use the methods correctly (as you have no damn clue what to use without checking the source code) so in 75% of the methods they convert the dynamic to an object and check if it contains "correct argument".

So what I have here is a code that isn't just hard to use, it's a hell to maintain.

So I talked with this with other testers on the team and they agree, but as most of them lack experience they couldn't talk back to the senior that wrote it. So I hope to sit down with him this week and talk this through because it would be fun to hear the arguments for this mess.

/rant

ARGH. I wrote a long rant containing a bunch of gems from the codebase at @work, and lost it.

I'll summarize the few I remember.

First, the cliche:
if (x == true) { return true; } else { return false; };
Seriously written (more than once) by the "legendary" devs themselves.

Then, lots of typos in constants (and methods, and comments, and ...) like:
SMD_AGENT_SHCEDULE_XYZ = '5-year-old-typo'

and gems like:

def hot_garbage
magic = [nil, '']
magic = [0, nil] if something_something
success = other_method_that_returns_nothing(magic)
if success == true
return true # signal success
end
end

^ That one is from our glorious self-proclaimed leader / "engineering director" / the junior dev thundercunt on a power trip. Good stuff.

Next up are a few of my personal favorites:

Report.run_every 4.hours # Every 6 hours
Daemon.run_at_hour 6 # Daily at 8am

LANG_ENGLISH = :en
LANG_SPANISH = :sp # because fuck standards, right?

And for design decisions...

The code was supposed to support multiple currencies, but just disregards them and sets a hardcoded 'usd' instead -- and the system stores that string on literally hundreds of millions of records, often multiple times too (e.g. for payment, display fees, etc). and! AND! IT'S ALWAYS A FUCKING VARCHAR(255)! So a single payment record uses 768 bytes to store 'usd' 'usd' 'usd'

I'd mention the design decisions that led to the 35 second minimum pay API response time (often 55 sec), but i don't remember the details well enough.

Also:
The senior devs can get pretty much anything through code review. So can the dev accountants. and ... well, pretty much everyone else. Seriously, i have absolutely no idea how all of this shit managed to get published.

But speaking of code reviews: Some security holes are allowed through because (and i quote) "they already exist elsewhere in the codebase." You can't make this up.

Oh, and another!
In a feature that merges two user objects and all their data, there's a method to generate a unique ID. It concatenates 12 random numbers (one at a time, ofc) then checks the database to see if that id already exists. It tries this 20 times, and uses the first unique one... or falls through and uses its last attempt. This ofc leads to collisions, and those collisions are messy and require a db rollback to fix. gg. This was written by the "legendary" dev himself, replete with his signature single-letter variable names. I brought it up and he laughed it off, saying the collisions have been rare enough it doesn't really matter so he won't fix it.

Yep, it's garbage all the way down.

"Big data" and "machine learning" are such big buzz words. Employers be like "we want this! Can you use this?" but they give you shitty, ancient PC's and messy MESSY data. Oh? You want to know why it's taken me five weeks to clean data and run ML algorithms? Have you seen how bad your data is? Are you aware of the lack of standardisation? DO YOU KNOW HOW MANY PEOPLE HAVE MISSPELLED "information"?!!! I DIDN'T EVEN KNOW THERE WERE MORE THAN 15 WAYS OF MISSPELLING IT!!! I HAD TO MAKE MY OWN GODDAMN DICTIONARY!!! YOU EVER FELT THE PAIN OF TRAINING A CLASSIFIER FOR 4 DAYS STRAIGHT THEN YOUR GODDAMN DEVICE CRASHES LOSING ALL YOUR TRAINED MODELS?!!
*cries*

I've been working exclusively from home for over 2 years now. I've been seeing several posts from people talking about adjusting to working from home, so I figured I would compile a list of tips I've learned over the years to help make the adjustment easier for some people.

1) Limit as many distractions as possible. WFH makes it much easier to get distracted. If you have roommates/family members at home, ask them politely to leave you alone while you're working. Make sure the TV is turned off, put your phone on silent, etc.

2) Take regular breaks. I find it easier to accidentally go hours without taking a real break from work. Try working in half hour intervals, and then taking 5-10 minute breaks. Read an article, watch a youtube video, grab some coffee/tea, etc.

3) When you eat lunch, eat it away from your computer. I often find myself eating lunch trying to wrap up fixing a bug, which makes it feel like I never really "took a lunch." Lately I've been trying to step away and do something else completely unrelated to work.

4) Get ready for work like you normally would. It's very easy to wake up, throw on your favorite pair of sweats and sit at the computer with messy hair half awake "ready" to start the day. Instead try doing your normal morning routine before sitting at your computer. It will help your mind and body go into "it's time to work" mode.

5) Keep your work area clean. I find it very difficult to work when my workspace is cluttered. Studies have shown working in a messy place tend to make us less efficient.

6) Keep your work area work related. Try to only have the things you need for work in your workspace. If you're working from your personal computer this can be difficult. I always end up with camera/music equipment left over from the previous night's photo editing/jam sessions. So try to clean off your desk when you're done for the night so it's ready for work in the morning.

7) Prepare for meetings. I have alarms set 10 minutes in advance so I can go from programming mode to meeting mode. During this time I'll go to the bathroom, grab a snack, water, mute all my email notifications, close any non essential programs, get my code ready if I need to present it.

Stuff is hard & stressful right now, but hopefully these tips will make it a bit easier. If anyone else has any good tips please share them.

Hello.

Is there anyone else who starts massive amount of projects and never finishes one?

It's a big problem when you lose time you should spent on orders because you work on that-amazing-idea that you'll drop few hours later.
I'm lucky as my employer thinks that all these unfinished stuff are pushing my experience forward, but for me it's depressing to not be able to focus on my work.

What do you do to fight with the urge to code that one more project? What do you do focus on the current work?

I've tried making myself a system for better client-programmer communication to keep myself motivated with better organised feedback and deadlines but ended up dropping it and sticking to terribly messy mailbox.

My coworker when he is copy pasting code without thinking..
Something like that:

var x;
if (veryExpensiveFunction()) {
x = veryExpensiveFunction();
// do something messy with x..
}

Sometimes I really feel the urge to punch him in the neck - and he never knows why I’m freaking out.. :’(

DON'T SUDO WHEN DRUNK

I rm-rf'ed my linux vm when i was drunk, and darn, it was wiped, clean and fresh

Ever had the feeling "My code is working fine but I know it's so messy and I should make it readable for others!"

-Never done anything

PM: Ok Android, i've reviewed the latest build, you are good to release. Waiting on iOS's build to test.

Me: ... are we not holding all builds until we hear back from backend about that bug?, as we likely have to change something on our side?

PM: Which bug?

Me: ... the only one we discussed yesterday in the team meeting.

PM: How many customers is it affecting?

Me: that we know of, one ... the CEO of our company

PM: oh that one, yeah were not doing that anymore.

Me: WHAT? i've been waiting all day / night to hear back. Why are we not doing this?

PM: ¯\_(ツ)_/¯ ... Everything is too messy at the minute anyway, the release plan is changing every day. Need to keep it back in line.

Me: ... the plan has changed exactly once. We had a plan at the start of last week for the last release, we changed it YESTERDAY to include 2 critical bug fixes. The only issue with the plan changing is nobody telling us these aren't bugs anymore

PM: We can discuss tomorrow in the team meeting.

CEO: oh hey guys, yeah we pulled that bug fix. Its not really a bug, more like a missing feature. No way it will get done before xmas. Going to live with the way it works for now and fix it properly next year.

Me: Ok, fair enough, but we really need to be told these decisions.

CEO: sure, sorry, didn't think anyone was blocked by this. What was the blocker?

Me: ..... you asked me yesterday to get this bug fix in the build ... you asked for the final build to be made today so we can go through the app store review. As we all discussed yesterday, today is kind of the last day we can really do this.

CEO: ok, its late, we can discuss this tomorrow in the team meeting.

Me: ..... ..... ..... ..... sure

Move to a new house...

My current cable setup.

So tidy....

Hired three months ago.

Trying to implement a feature the heads were long waiting to have. It involves a part of codebase so messy and complex that even senior devs were afraid to touch.

Made a prototype, finalized related stuff, merged to develop. Got praises at the demo meeting.

Feeling like Frodo after his quest 😳

I am an atheist but sometimes I thank Jesus when a change to some old messy code actually works

Not sure if I should be happy of I should cry.
...

I woke early today so I could directly start working on my little project to make some progress.
I was coding for ~10 hours.. The code worked fine for all testcases, except for one. I debugged for hours and I couldnt figure out what was wrong. I tried changing stuff in my code and it got more and more messy to the point where I couldn't even understand my own code anymore. I was so frustrated ...
> Deleted everything I made today.
> Rewrote the entire thing in one hour with a different, more structured approach.
> Worked perfectly for all cases, even the very complex ones.

1 day wasted....

Should I be happy that I came up with something decent in the end? I am still mad cause I wasted the entire day.. Why did I not directly went for the thing I did in the end ..? ._.

Last week, the team lead told me that he can't merge because my code has code smells and going forward, can't have that. We use Sonar and well the way to "fix it" according to him is to mark the line using //NOSONAR.

Most of the issues are minor like Unused imports and for me incomplete TODOs.

And before the "verbal" rule was only need to fix Major + issues. And well the reason I use TODOs is to mark code that probably needs changing in the future. I know there's going to be some feature that these lines have to be changed. But the requirements are fully defined yet from business.

But I sort of blew up on him. YOU WANT TO ENFORCE ZERO CODE SMELLS NOW?!?!?! AND THESE MINOR ISSUES? MARK THEM WITH NOSONAR?

HERE'S WHAT I THINK FOR THE LAST X YEARS... THE CODE DESIGN IS SHIT, MINOR CODE SMELLS AND MANUALLY MARKING THE ONES U NEED TO KEEP... ARE THE LEAST OF OUR PROBLEMS...

THE OTHER PROBLEMS I'VE MENTIONED BEFORE EVER. MOS YEAR BUT YOU DIMWITS NEVER LISTEN.

YOU THINK MY TODOS ARE BAD... 90% OF THE CODE AND FEATURES (THE ONES NOT DONE BY ME) LOOK AND SMELL LIKE MONKEY SHIT. UNDOCUMENTED, MESSY, FULL OF BUGS.

AND GUESS WHAT? NEW FEATURE, SOME DEV FORGETS TO CHANGE SOME COMPONENT THAT DEPENDS ON IT. WOULDN'T IT BE GREATE IF THERE WERE BOOKMARKS... O WAIT...

i just was catching up on comics again and saw this one... with triggered my memory and this rant... My first thought was to forward it to him...

Some people say my desk is too messy...

I think I just need a bigger desk. 😋

Opinions?

Joined a new company...
It's been a week since I joined.I feel like shit.
There are over 20 employees, however I didn't had a chance to chat with a single person for more than a minute or two. Not a single meaningful or even a shitty but personal conversation. I'm trying to strike up conversations whenever I can, but there are no possibilities to do so. I think they have a few chat groups where I'm not added. At lunch time they suddenly start running to a guy that gathers the money to buy lunch, i saw that and joined, but I'm 99% sure they are communicating/speaking on some kind of chat.

I joined as a front-end developer, however I'm not sure if I'm a junior or whatever here. On the first day they showed me the system, they are using PHP and jquery + es6, the structure is messy and I'm not used to it It should be MVC-like, but messier, but it's not like anything I have seen. I usually work with opencart / cakePHP style systems. There are js files with a lot of custom funcions and sometimes there are functions that have mixed jquery and es6 inside script tags top or bottom of the view files. There are a lot of code that I don't understand, on the third day they gave me a task - to remodel a view (basically one page in the cms) I did it, but they didn't check up on me untill the next day, I gave them some notes on the task I finished, and I started making some of the code easier to read for myself after I was done. They didn't really gave me a new task, and I don't know what to do, don't have anyone to ask about what to do, because there are only 2 developers here, and the other guy is on vacation. The boss is also a coder, but he's never here and I feel like I shouldn't be asking him stupid coding questions, because you know.. He's a boss. I understand a lot more of their PHP code then their js/jquery. I feel like I'm stupid and I don't know what I am doing here and what I will be doing here in the future. I did move across the country to join this company, and if this won't work out i have a rent contract signed for a year. Today I was looking at the clock for the last 2 hours of the work day and waiting untill I could get out of there. To say that I feeling like shit would be an understatement.

I don't have anyone whom I could ask for coding advice outside of the company. Fuck.I have worked in a few companies before, but there was always an introduction to the staff, and or the working environment and usually there was a person that I could ask questions on the regular. This company is bigger however and I'm not an emotional guy whatsoever, but I feel like I will start crying.

A turret (white) from Portal 2

A silver RWBY logo

Two foam dice as memorabilia from my previous job

A plush 😈

Plus a collection of various things saved and hidden from the scary hands of destructive children monsters.

We used to have a portal gun (both full size and mini) and a gravity gun on the dresser. But with the advent of children, they’re safely back in their boxes.

I got my first programming job half a year ago, the lead developer there is really fucked up... he is old fashioned and stubborn as hell. He developed a platform that is a mess, his comment: “it works”... but now I have to fix it... I argued with my boss and convinced him to put more time in making it more scalable and feature proof. But the lead developer back then... he didn’t agree it seems like he want to do everything as quickly as possible... now half a year later he stopped working for us and I’m the lead developer now.

And I’m discovering more and more bad decisions... HOWWWW

WHAT DID THIS GUY DO???

At one time I was arguing with him and he backfired a comment: “I’m doing it like this for 10 years”... so I guess that’s the problem... he didn’t put effort in keeping up with the latest developments...

There is literally no structure in his work, every file is different... HOW DO I FIX THIS IN A NICE WAY??? I’m thinking to just start over again...

"iOS Development is easier"

Yeah, right? There's no dropdown, no checkbox, no radio button, no placeholder for multiline textfields, ...

Motherfck!

You have to manually do everything yourself and lay things out in their messy slow Xcode. Apple doesn't include important things only because they have randomly decided not to include them! Fuck this job.

I've told the same story multiple times but the subject of "painfully incompetent co-worker" just comes up so often.

I have one coworker who never really grew out of the mindset of a college student who just took "Intro to Programming". If a problem couldn't be solved with a textbook solution, then he would waste several weeks struggling with it until eventually someone else would pick up the ticket and finish it in a couple days. And if he found a janky workaround for a problem, he'd consider that problem "solved" and never think about it again.

He lasted less than a year before he quit and went off to get a job somewhere else, leaving the rest of our team to comb through his messy code and fix it. Unfortunately, our team is mostly split across multiple projects and our processes were kind of a mess until recently, so his work was a black box of code that had never been reviewed.

I opened the box and found only despair and regret. He was using deprecated features from older versions of the language to work around language bugs that no longer existed. He overused constants to a ridiculous degree (hundreds of constants, all of which are used exactly once in the entire codebase, stored in a single mutable map variable named "values" because why not). He didn't really seem to understand DRY at all. His code threw warnings in the IDE and had weird errors that were difficult to reproduce because there was just a whole pile of race conditions.

I ended up having to take a figurative hacksaw to it, ripping out huge sections of unnecessary crap and modernizing it to use recent language features to get rid of the deprecation warnings and intermittent errors. And then I went through the same process again for every other project he'd touched.

Good riddance.

Back then, whatever finished tasks I have done, our CTO always contradicts my idea and finds a way to humiliate me. I don't get the point why he did that. Probably, he didn't want me to excel at something or he really does have crab mentality. I already reported this issue to our CEO because I was being harassed and submitted my resignation letter.
And boom! Guess what? It looks like our CTO just stepped a chicken manure and treats me nicely like a princess.

P.S. To be honest, it took him like a couple of months to step down and act normal like nothing happened. Really appreaciated the A-ffort, though!

I once worked at a small dev shop with a team of about 5. I was the lead but I was also the only backend developer. Since it was such a small company I also managed the Datacenter... which we had in our building. It was messy, but impressive. Although I seemed to be always stressed and felt like my job was always on the line... I do miss how excited I got when I learned something new. I was then able to talk to my boss about how excited I was to learn it and I can't wait to learn something new. I'm sad because I don't get that excited anymore. Now, I'm not really learning anything new, I'm just posting my skills as a developer. It really bums me out. I only wish that I had a degree in computer science so I can become a teacher and see my students get as excited as I was.

Messy desktop :P

First day on my first job ever, the boss asks me what I want to do. I indicated that I had some experience with php and the yii framework (which was at some point very cool xD), so I wanted to start with something like that. And so it goes: after two days of watching laracasts (which is an awesome platform by the way! :O) I got assigned to a project.

Now the company I work at uses some kind of self built system that tracks how many hours are spent on which project, and compares that to how many hours was estimated implementing a feature would take. That's cool, but then I saw that for the project I was working on the time estimated was 5 work days. This was the estimate for both designing the interfaces and implementing both front and backend. I knew in advance that this was probably way to little time for me, but didn't want to come over as the new kid who can't do shit x)

Anyway, I started on the project and was having fun, but the biggest time consuming aspect of the project was not necessarily that I didn't have enough experience: it was that the developer who started this project and made most of the design choices had written some very messy code, without tests or apparently any refactoring. Also, everything was extremly inconsistent and not according to all the best practices I just watched in my laracasts spree.

So fastforward a little: we're way over the estimated hours. Yay. Now suddenly the boss comes by with an almost angry face that the client is becoming angry and we need to finish soon. He makes it entirely our (me and the front end guy) problem and I just decide to say nothing and try to work faster.

Now I'm stuck writing fugly code on top of more fugly code and when I mentioned to my front end guy that I was almost finished with feature but I only needed to finish up the tests, he said something like "oh just don't write tests, that'll take too long"... Is that really the mindset of this company?! No wonder the project I work on was in a very bad state.

Thanks to devrant I see now that I just need to say something if I know that I won't be able to complete something in a certain amount of time and that other people are just like me (thank god). :) I think I'll need to post more rants to vent my frustrations x)

This is how chrome reacts when you open 100 tabs on your phone

Me: what happens if you type 'echo PATH'? Pipe it to a file and send it to me
Collaborator: *sends me a 17,238 character text file of their PATH contents*

Me: that's no PATH; that's a space station

I do think C# is the best language going. It's basically got everything, and VS is, weirdly for a Microsoft product, among the best IDEs. You get to thinking that it's actually harder to write unorganised code than not with it: it becomes difficult to imagine writing messy, repetitive or spaghetti code in C#.

Then you use Unity.

One of my former coworkers was either completely incompetent or outright sabotaging us on purpose. After he left for a different job, I picked up the project he was working on and oh my God it's a complete shitshow. I deleted hundreds of lines of code so far, and replaced them with maybe 30-40 lines altogether. I'm probably going to delete another 400 lines this week before I get to a point where I can say it's fixed.

He defined over 150 constants, each of which was only referenced in a single location. Sometimes performing operations on those constants (with other constants) to get a result that might as well have been hard-coded anyway since every value contributing to that result was hard-coded. He used troublesome and messy workarounds for language defects that were actually fixed months before this project began. He copied code that I wrote for one such workaround, including the comment which states the workaround won't be necessary after May 2019. He did this in August, three months later.

Two weeks of work just to get the code to a point where it doesn't make my eyes bleed. Probably another week to make it stop showing ten warnings every time it builds successfully, preventing Jenkins from throwing a fit with every build. And then I can actually implement the feature I was supposed to implement last month.

I’m pissed.
I had previously ranted about being assigned to a very messy project. I spent 3-4 months alone adding features and CLEANING things up.

Recently, there had been talks about a new major development phase on this project. But things lingered and the day before I’m to go on vacation, I get the news that this new phase starts in 2 days. Since I’m going to be on break they’re putting other guys on the project who don’t know anything about it.

Fast forward two weeks later.
I’m back from vacation.

I find out one of the guys has strong opinions about doing things certains ways… but unfortunately they are "ways" of unnecessary complexity, abstraction and verbosity.
After just a couple of weeks I’m already lost in the complexity of his code, which supports features of VERY LOW complexity. Fuck, has he ever heard of KISS? Has anybody heard of it where I work?

Now I have to spend my mental energy trying to make sense of this pile of crap rather than actually spending it getting things done.

Before becoming a developer, I used to work as a sales rep at this company that spent a good amount of time building what they believed to be an innovative state-of-the-art “code generator”. It was basically a scaffolding tool for generating software.

They were using it to auto generate customized iOS and Android native mobile app templates, along with a web backed.

The problem was that the generated code was shit, and the developers on the team basically spent more time fixing bugs than if they had built everything from scratch. But their passion for the product meant they just kept using it.

For some reason they never fixed issues in the original templates, so basically all the bugs that were found, kept showing up with each new app!

I have never seen apps like this that essentially had more bugs than features. Opening more than 10 app screen meant the app would freeze and crash. Sign up forms were actually dummy forms. The list goes on...

All the apps had the same shitty UI. For example, Product pages had a product image area that was like 5% of the screen view!

Last but not least, apps had a backend IP address hardcoded pointing to a server with an IP address that was temporary. So one day they had to restart the server and suddenly all customer apps stopped working and required a software update to work!

It was amazing seeing how a team of 3 developers trying to fix messy autogenerated code, couldn’t accomplish what was essentially a website on an app that I managed to build in my free time.

That’s how I knew it was time to quit my job and code full time.

this code is messy .. it has to be refactored..

abstact those classes to commom interfaces .. create a base class for all those common classes .. make this a parameter, make that a setting.. generalize this, pass a behaviour to that.. separate responsobilities..

hmm .. need to handle that special case .. let's just add a temp method for now to get it compiling .. //todo this later .. maybe add a couple virtual bools to handle the base class behaviour

238 compilation errors! .. let's do a static var for now on this.. and just add this for backward compatibility .. maybe hardcode that dll name, I know it'll NEVER change..

aah finally, all compiles..

oh..

this code is messy .. it has to be refactored..

Simple setup with a messy white board!

Idk why, but to me, the design and looks of Skype app feels kinda messy and creepy :/

My company’s code base is so messy that the dev branch and master branch is so buggy. But they put the blame on me as usual.

I use git blame, I wasn’t the author .

>be my team
>developing a mobile app
>I'm responsible for developing a "RESTful" API to interface communications between the app and the database
>there's also an "admin" web application which the client themselves will use to manage some shit in the database
>I've developed the API, it works with the mobile app
>instead of just making it simply a front-end app that makes requests to the API like the mobile app does, the guy responsible for the admin app completely ignores my API and implements his own with a certain messy dollar symbol language and a certain bloated piece of server software, accessing the same database directly, and does some operations in his own special way that will break what I've implemented
>now data inserted via admin app is inaccessible to the server API, and I'm expected to "fix" my code so it's consistent with this guy's shit, but the only way to do it is introducing interdependency between the actual API and the admin app's back end

Fuck my life, now I'm the one responsible for the app being broken because no way the guy who's used to kludging unmaintainable shit together fast would ever fuck anything up

Customer: We need an app to replace the Excel ( bunch of forms with messy macros and script)

Also Customer: Can I export the form fill it in an excel and import again.

Me: Sure, Definitely
Inner me: Where's Thanos

Messy and fugly codes makes my head hurt, but when it's mine, it makes my heart bleed. :'( </3

When your pm forces you to push new features out too quickly and you're slowly digging yourself into a messy hell, knowing you have to one day refactor thousands of lines of code.

I practice what I call "Aggressive Oriented Programming" or AOP.

Whenever I'm investigating a bad bug, working on a project that I really hate, or dealing with messy code written by a messy developer, I often find myself resorting to an [internal] state of violence.

It's not like I scream and smash my screen (although sometimes I want to). It usually consists of a few git blames and some curse words in print statements for debugging. This is just my way to vent.

So I've taken over a project, well, not really taken over, we've been hired to add more functionality to a Wordpress site.

I have never seen such a messy code in my life... variables have mixed languages, indentation is a mix of tabs, 2, 3 and 4 spaces, camelcase, snake case, short names, long names. ' and ", no spaces after commas (gotta save those bytes doode)
Almost like it has been copypasted from everywhere.

I think I said 10-15 hours for it. I think I will spend a lot more time tidying up this code.

Hey, look, 3 index files!!
index.php
index__backup.php
index__backup_2.php

I don't dare to look into the CSS or JS, but I know I have to

My i3-config got so messy, I'm tempted to just start over with a new configuration.

Fffffuuuucccckkkkkkkkkk!!

My team and I had a presentation scheduled and we worked on it for more than a month.

A bloody fucking month long preparation.

We went through multiple reviews with stakeholders which weren't necessary and no other team does.

I put on some music to lift up my energy levels while I waited anxiously.

Show time.

We have one of the largest city festival going on this week.

The community in neighbouring building started reciting prayers out loud on a PA system just when the presentation began.

~40 folks and me struggling on video to not lose my cool and fuck my luck, I went nervous because I couldn't focus.

That's when my big boss pointed out that there some background noise and I had to explain it to them.

My very first presence and I forgot to even introduce myself. What a nut head I am.

I am annoyed and angry at myself. I perform well impromptu over planned and preparedness.

Thankfully my team mate who talks a lot and my designer, handled things well and saved the day.

Massive respect for them and kick in nuts for me.

Uuugggghhh!!

Also my neighbour is renovating his entire house and since I am using it as my workspace, I literally sit in between junk and cement and wires all around.

What a messy wasted day it was.

Anyone else here who uses the 'clear' command excessively on unix systems?

I hate it when I want to move on to the next thing I have to do with a messy screen full with text, cls and clear are my favourites

!rant

Got back into android development recently and while everything was pretty flawless ( I managed to get the basic concepts implemented in a day) something wasn't right.

For some reason I was not happy with the code i wrote, although I took examples from google and tried to adapt their code style. It looked aweful. I hated my code.
But the code itself wasn't the core of the problem. I could easily add new features and replace components with new implementations without breaking the app. All those "good code quality" identifiers were there.

Turn out the problem is Java. Or to be more specific: Java 1.6
Every listener which only calls a single function once a worker has finished needs 6 lines of code. If you implement the inferface in the class it gets messy once there are multiple workers and you have a generic interface. And there are no lambdas!

So I made the switch to Kotlin.
The app was converted to kotlin in 30 Minutes​. Android studio can convert the classes automatically and very little manual work is needed afterwards.
After that I spent 2 hours replacing the old java concepts with Kotlin concepts: lamdas, non-nullable types, getters and setters in kotlin style (which in this case is c# style) and some other great thing.
The code is good looking now. I like it. I like kotlin as it has a lot of cool things.
Its super easy to learn. It took me about 2 hours to get into it. It combines concepts from java, javascript, c# and maybe a few other languages to form a modern jvm 1.6 compatible typesafe language.

Android dev is fun again!

I see now why people can despise WordPress.

2nd week of just pure learning and I gotta say that I can see that the way it was built was paved with good intentions, but it's clear people wanted more from it and things have only gotten more and more messy.

Honestly, it's fine. It's not my favorite stack, but whatevs.

Do you too, always experience the programmer's "can problem"?

When you write a messy code and it works perfectly the first time

So this phallus decided to make my day a night mare, I coded the Interface in separate class for each distinct services, He just told me to re write it to one class, before he don't understand it.

I wrote documentation, he said it is not professional. and now the fucking codes are containing redundancies.

For instance if he use my method, all he need is call my function once, and call it everywhere. But now the code is messy as fuck, calling the same thing over and over again which can be done by separate it to a function once, and reuse it.

Is this a bad way to traverse corners of a cube?
The objective is obvious from the context and I assume that programmers know how binary works.

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.

older clients are returning with my old projects and asking for improvements, I did buy a few very shitty scripts from the internet/ and used one of my friends custom php cms for the other client because I REALLY needed money and they needed the projects yesterday.

Now I'm looking at the code and can't start working because of how messy it all is, I want to remake it all with a good framework and system, but it would take too much time (and they want it fast) and they wouldn't want to pay for the improvements because what they have now works..

I guess the shit you throw out when you're younger does come flying back like a boomerang..

Operations: Can you exclude some user records for the website? These are obsolete and we don’t want users to access these anymore.

Me: So what are you using to indicate the record is obsolete?

Ops: We changed the last name field to say “shell record - do not use.” Sometimes it’s in the first name. Actually, it gets truncated to “shell record - do not u”.

Me: A…text field…and you’re totally ok with breaking user accounts…ok ok cool cool

Not cool 😳😬🤬 I’m not causing more chaos because your record keeping has gotten messy

when your code is messy af but somehow compiles and still works!

My desktop used to be so messy, and organizing files was a pain. So I created a small script that would create folders based on file extensions. Now instead of hundreds of files all messily placed in one folder I have 10 folders with all the files seperated by extensions

It began when I was tasked with creating a better and more engaging experience for our new Facebook page. This was in Facebook's early days, so there were not really any "best practices". We were making it up as we went along. I decided one way would be to game-ify things, since gaming, at the time, was a Big Deal on Facebook and people were starting to use it to build customer funnels.

Grasping for low-hanging fruit, I decided a Tetris variant around our topic would be fun. I had to hire a dev because at the time I was a static HTML web developer just getting into social media management. I knew nothing about game development or how to use Facebook's API for such things.

Long story short, we got about $10,000 (FB app devs came at a premium then) into the project when I came across a very recent article about the history of Tetris games. It said that even though Tetris had once been considered for all intents to be public domain due to it being created by a Russian coder during the Cold War, it had just been acquired by an IP protection entity that was charging royalties for any variant of Tetris created from a specific date onward and paying the original developer. So, even though I thought I had been thorough in my initial permissions checking, it turned out we were gonna be in deep doo-doo with licensing fees and restrictions if we released this game to the public.

I had to call my boss and admit my error. She was FURIOUS and really gave me an ass-chewing over it. I then had to call the marketing person whose budget I'd been slaving away at wasting. She was a bit more forgiving (her budget was in the millions). Then I had to call the corporate legal department and explain what was going on. They told me to immediately pay any outstanding hours, then fire the dev but not before getting him to send me all code and assets, deleting his copy, and then, upon my receipt of those assets, deleting MY copy so that nothing of it ever existed. And I was supposed to say _nothing_ to the dev about why he was being let go, so that there would be no "trail" leading back to this fiasco. (The dev hounded me for weeks asking what he'd done wrong. It killed me that I was bound and gagged by corporate legal and couldn't tell him.)

I was in so much trouble. I was literally in tears over it. I'd never wasted that much money in my life. That incident pretty much sealed my fate as far as any trust my bosses ever put in me again (not much at all). I was a bit of a pariah in a lot of ways for the next 5 years whereas I had come onto the team as a young social media rockstar at first.

After that, and a couple of other bad scenarios that were less my fault and more due to a completely dysfunctional management and reporting structure, they eventually "transferred" me to another team. Which was really just a way of getting rid of me by sending me to a department that was already starting to outsource overseas and lay people off. It was less messy that way. I was in the first set of layoffs.

Since then, I've had a BIG fear of EVER joining a large corporation EVER again. I prefer to work for small businesses now, even if I get paid less. Much less stressful from an office politics and impact of mistakes standpoint.

Somewhat messy, too lazy to clean it all up ^^'

And I really need a Dual-Monitor setup again .-.

Our tech lead left a mess in the database. He turned his screw-up into an architectural discussion, weighing the benefits of duplicated, messy data vs. keeping it consistent. He suggested that, instead of fixing his broken script and cleaning the mess, we should break all of the other scripts and have them trash the database, too.

They almost believed it.

What a clever maneuver. I wish he would use his cleverness to make good software, instead.

public class Main {
public static void main(String[] args) {
System.out.println("Hello, World!");
}
}

sorry for my messy code

Do you ever just think of a feature you want to implement in your program, thinking it's going to be a challenge and then you realize "oh, my program is set up in such a way that makes adding this feature literally one additional line and one modified line of code, without making the code messy"?

<rant>
Don't fucking tell me to move business logic from the service to the controller. Don't fucking tell me it will enable an "event driven architecture." Don't fucking use Angular for this project if you're just gonna shit on best practices and write convoluted, messy, inconsistent code and force your coworkers to do the same!
</rant>

Am I the only one who reinstalls their os every month because it gets messy?

Well my home office is a proper mess currently. It isn't so much an office as a corner desk in the child's nursery, but house hunting went on hold.

It features the likes of my devrant ducky, crazy aarons thinking putty, a stuffed gnu, and a galileo thermometer among other paraphernalia; also a plastic goat that screams when I push down on it. That last one is a huge help to me these last few weeks.

interviewee : *Appeared for JavaScript interview, in shorts with messy hair *

interviewer : why are you like this *with disgust feeling*

interviewee : I exactly don't know what this refers to

interviewer : can we talk about package

Dear Tailwindcss,

Fuck you.

Fuck you and your messy as fuck html files.

Fuck your shitty pseudo 90s 'Let's dump all our shit in a single html file'.

Fuck your claims of being responsive, most of your widths and heights are done in FUCKING PIXELS.

Fuck your claims of being flexible, adding a 10% width class took 20 minutes of scrolling through your shitty docs.

And the worst part is, the poor devs 4 years from now are gonna be stuck maintaining this goddamn shit because shitty enterprise companies desperately trying to stay relevant are treating this shit like the Holy God of Frontend styling, the solution to CSS once and for all

FUCKING IDIOTS CSS ISN'T BROKEN, THIS GARBAGE IS!!!! WE DON'T NEED A SHITTY SOLUTION TO A PROBLEM THAT DOESN'T EXIST

Tailwind can go fuck itself with it's 200 character html lines

Dont become a dev if you:

- Cant sit in the office for 8-10 hours a day

- Dont know how to google information/ errors, instead you interrupt your teammates with stupid questions every 5 minutes

- Are a perfectionist and don't like constant change.

- Are neurotic and give up easily. If you get triggered about broken or messy things to the point where it ruins your day to you and everyone else around you. You need to separate your work from your life.

- Don't have good communication skills. Worst I saw was a guy who speaks with a stutter(nobody understands him) and also writes very poorly (nobody understands his emails). Also he gets very angry when you ask additional questions to clarify what he said. How can you work with someone like that?

- Are very sensitive to critique. I prefer someone telling me that my code is shit and telling me why, instead of feeding me delusions and false validation.

- Dont know how to balance working in team and working solo. Nobody likes lone wolfs who are arrogant and not in sync with the team. But also nobody likes to drag teammates who cant think for themselves and even after years of spent in the field are required constant spoonfeeding because they are unable to google and teach themselves with trial and error.

I don't have any 'home setup' (it's just a laptop), so instead I'll post my office one.

It's always a bit messy, so bear wirh me :p

When you get back to the office and remember the mess you were tackling on Friday 😅

I don't know if we can be friend...

I don't like cable art, my desk is messy(no setup), no stickers on my mac, don't care I have to use mac or pc or unix, I don't code at night.....anymore, I don't have problem with ;

But....I love coffee.

My code be like:

Call the method cronk...

WROOOONG MEEETTTTTTTHHHOOOOOOOOOOOOOODDDDDDDDDDD!!!

*climbs out of alligator pit*

Why do we even have that method

Needs tidying and I’m not exactly using it for work at the moment... but this is my home office / bedroom setup.

There’s an Alienware Alpha hiding behind the MacBook, but it hasn’t actually been on more than once since the MacBook came home... 😂

"Ok guys. These files are just too big. If we change 'function' to 'f' - and 'var' to 'v' - and just make every keyword and variable possible: a 1-letter key, things will be much tidier and I can get back to focusing on work. It's just too messy."

White ones are hand made stickers from my gf as a present. Their cuts are kinda messy because of I literally messed up while cutting but i think i really liked them.

when a senior dev says your code is messy just after you finished refactoring 😞

Synonyms of counter:
i
j
k
x
#loop

I'm a TA myself and just yesterday wanted to defend my fellow TAs and CS/IT teachers from some of the rants here. Of course not all of the rants are but I found a few quite unfair towards us and I can fully understand a TA getting confused and tired after 5-7 hours of helping and wrapping your head around some of the harder problems the students run into.

However, I'm also a student myself and right now I'm fucking fed up with the shit my supervisor gives me regularly .. So let the rant flow!
(disclaimer: the following text uses “you” to address the rant recipient. So, dear reader, don't feel offended)

First of, why do you fucking care when and especially where I'm working on your project when you know I'm only working part time since I'm usually tutoring students by daylight. Having me come in after my TA shift to work on your project instead of letting me go home, get some rest and food, and start working with a fresh head is neither helping you nor very productive. Also, if you want me to be productive and use your fucking tools to get going faster you better not make me fucking debug your fucking tools. For instance, I don't even have the same first name so all your fucking paths are invalid on my fucking machine! Also, I get that your machine is more powerful than mine and I don't really care about it as long as you don't fucking push convoluted messy timing sensitive scripts and make me search for the correct values on my machine. And, if a file your script is trying to delete is not there aborting is not an valid exception handling!

And don't get me started on the scripts that actually do some work besides setting up your fucking toolchain!

Refactoring some of your messy code into something simple and easy to read is so satisfying. 👍

I'm not a developer by profession and my home setup is always messy (where I develop personal projects) but I am an intern sysadmin so here is my office desk :) wanted to join the whole show your desk movement

Pardon me if the tags are not right. Im fairly new and mostly a reader.

Proudest bug squash? Probably the time I fixed a few bugs by accident when I was just trying to clean up an ex-coworker's messy code.

So I used to work with a guy who was not a very good programmer. It's hard to explain exactly why other than to say that he never really grew out of the college mindset. He never really learned the importance of critical thinking and problem-solving. He did everything "by the book" to a point where if he ran into an issue that had no textbook solution, he would spin his wheels for weeks while constantly lying to us about his progress until one of us would finally notice and take the problem off his plate. His code was technically functional, but still very bad.

Quick Background: Our team is responsible for deploying and maintaining cloud resources in AWS and Azure. We do this with Terraform, a domain-specific language that lets us define all our infrastructure as code and automate everything.

After he left, I took on the work to modify some of the Terraform code he'd written. In the process, I discovered what I like to call "The Übervariable", a map of at least 80 items, many of them completely unrelated to each other, which were all referenced exactly once in his code and never modified. Basically it was a dynamic collection variable holding 80+ constants. Some of these constants were only used in mathematical expressions with multiple other constants from the same data structure, resulting in a new value that would also be a constant. Some of the constants were identical values that could never possibly differ, but were still stored as separate values in the map.

After I made the modification I was supposed to make, I decided I was so bothered by his shitty code that I would spend some extra time fixing and optimizing it. The end result: one week of work, 800 lines of code deleted, 30 lines added, and a massive increase in efficiency. I deleted the Übervariable and hardcoded most of the values it contained since there was no possible reason for any of them to change in the future. In the process, I accidentally fixed three bugs that had been printing ominous-sounding warnings to the console whenever the code was run.

I have a lot of stories about this guy. I should post some more of them eventually.

So when code is badly written, more corner cases are unnecessarily introduced. And it’s sometimes tricky to find the corner cases and probably messy to fix the corner cases.
And so the code grows in size as a result. And when these fixes to the corner cases are not well done, they introduce more corner cases.
So what results is a large collection of corner cases. Only corner cases remain when this goes on for a while.
Because of this, every new feature can be effectively translated to a collection of corner cases to be implemented.
As corners grow, triangles become circles and tetrahedrons become spheres.

I live in such a sphere.

I really want to stress that we should add the ticket for adding the missing test cases in *this* sprint and not postpone it any further.

-- "Isn't there something more important to be added instead?"

There. ALWAYS. Is. Something. MORE. Important. The real problem was that we implement the test cases in the past to begin violating our definition of done. We have to fix and one point and we have to own that decision as nobody else will care about passing tests and test coverage. It's our job to care for that.

Yes, we can instead focus on all the other high-priorities task that should have been done yesterday, yet that won't change the fact that large part our codebase will remain an untested messy blackbox just asking for weird bugs and wild goosechases in the future.

Don't hide behind "high priority tasks". A job is done when it is fucking done and tests are part of that. Hurrying from one important task to the next will just mean we'll never do it. There is no better time than right now.

If code coverage got left behind in the past, then we'll have to suck it up in order to fix it as soon as possible, otherwise we'll just suck forever.

so, flexbox.

and my only question is: why did it take CSS 30 years to get the features which it should have had from the start? now because of that, even this awesome thing is messy due to how the old features collide (or don't collide, i'm not entirely sure tbh) with it.

but maan, flexbox! now at least a part of css feels like a tool made to solve the problem it's supposed to solve, instead of layers of hacks that you can somehow hack into having the side effects which result in it doing what you want it to do!

I thought it is an IDE 😜

There is nothing on my messy desk other than never ending work. Damn, I need to get something. What can I get,

* a toy : not my kind of stuff
* a bike : not enough room
* a small plant : hard to find in the dessert (uae)

Damned.

Laravel is clean but slow
Codeigniter is fast but messy
Which one to choose?
Or are there any good alternatives?

I once thought that developing on WordPress was cool and easy. Now I see that it's a total abomination.

No more WordPress job for me. I'm gtfo.

We’re a young and dynamic team of messy data-scientists who have failed at being employed on the real market. Our experience in losing data and throwing files away is more than amazing! Over the years, we have managed to get rid of so much important data at home and even at work. Pictures of our holidays, important invoices, login details… it’s all gone. So we started to make a business out of what we’re good at.

A client asked for a tool for his website. So I built it for him and he was satisfied with the thing, cause it did what it should. Nevertheless I was not, because it kind of had a messy backend. I made it working and charged my time. Now I am wondering if I should rebuild the thing to satisfy my code quality for free, or just keep that thing as ugly as it is....

What your opinion on this?

I'll tell you the only time... The only times I'll fuck up.

When something changes. That's it.

Nothing else causes me to fuck anything up.

My code gets more and more messy the more people go oh change that ,😐 can that be a capital .... Hold on that box should be smaller

😤😡 Messy = I fuck up.

Now that might well be something I need to work on !

But if you send me twenty emails all with minor things that take seconds to change 😡 I will care less about your project , that makes me lazy.

If you want your project to be perfect on launch .. one plan a couple round of amends maybe 3 and your golden

But I can not keep checking if your application is all good after these minor changes 😐 (these are not situation you can write tests for)

Yes it makes me an asshole I'm aware , but I've been awake 40 hours fixing these peoples work, and quite frankly I couldn't give a toss

Every work experience so far.

The first one... Internship abroad, very messy codebase, almost no code review.

At the end I was so tired I started watching movies during worktime.

Want to get back to your code the next day?

Leave it a little messy.

When a dev leaves a project in the middle, and someone else has to continue their shit, that's the worst fucking thing ever!
3000+ lines of codes in just one class? Fuck!
I don't even know where to put my code, where to put debugger break points, where to... fuck fuck fuck!!! >_<

> be me
> be developing a react native app
>realize the iPhone X notch is clipping your content on the first/home screen of the app
>google says: simple fix
>find a built-in react native thing to add safe area padding
> refresh the app
> ohno.png
> the other screens with navigation bars already have built in padding
> TOOMUCHPADDING.jpeg
> remove safe area thingy
> finds a clever, not particularly hacky way to pad the home screen without showing the header bar by setting its height to 0 and the color to match the content background
> more-problems.app
> there’s a small 1–pixel light colored line separating the header from the content clearly breaking the otherwise continuous single color background
> google.sh
> wtf.txt
> stackoverflow.html
> no responses except something I’d already done
> keep experimenting
> tries basically everything to figure out where that line is coming from
>sets borders to thicccc and bright red
>no bottom border? Ok that’s not it
>opacity?
>forgetaboutit.mov
>try shifting the header position around by a few pixels? Maybe it’s misaligned with the white parent layer underneath?
> nope.jpg
>it’s past bedtime
>Sleep.jpg
>thenextday(today).zip
> what about the content? Is that misaligned?
> nope2.jpg
>Maybe its an iOS feature not a react thing?
> make a test Xcode project, completely native to test
> negative.dng (pun intended)
> more-furious-googling.mp3
> find a native iOS stackOverflow question with the same issue (1px line)
> realize your Xcode test wasn’t done properly.
>atleastimmakingprogress.iso
> start looking into the SO post
>it’s native so I have to find out how to do it in react-native
>invent a bunch of style parameters that don’t exist in the documentation to see if there’s an undocumented thing
>loadsaloadsaerrors.log
>googles for a react native version of the iOS only SO post
> somethingpromising.tar.gz
> *tries it*
> “Haha nope” -my code
> whataboutthisotherthing.bin
> KENSISHSBUCNEGWISBVSIDNRVSIDNFIRJRBDKFNFIDJFIFKFNR
> HOLY FUCK
> IT WORKED
> AFTER TWO FUCKING DAYS OF SHITTERY AND SHENANIGANS
>AND MANY STACKOVERFLOW EDITS TO A NOW VERY MESSY POST
>THEREISNOMOREBORDER(final).zip
>*screams of relief*

Hey devs, really need some help here. This is driving me crazy...

We're currently taking issues from the company via mail. We've got a group mail that goes to the three of us at the IT department. Problem is, colleagues just forward customers emails without event trying to help, which means that we get stupid issues like "I can't sign in", and no further information. We're currently using Jira, and I was thinking perhaps we can set up a Jira Service Desk? Then we could have an internal help desk where issues could be submitted, and require some important fields, and perhaps add a checklist. Have you had any experience with Service Desk? Do you think it would be a good idea to have a "normal" person have an account there as well to filter out the normal "Have you tried restarting your computer" stuff? Is it suited for non-developers?

Any other ideas?

Yeay, messy question, but I'm fucking desperate...

My beautiful code now transforming into ugly messy code. Damn you deadline 😠

How it started:

Need to replace in a lot of SQL files certain stuff...

find . -type f -iname '*.sql' -exec sed -i 's|new|old|g' {} \;

12 hours later that find executed a shell script containing roughly 120 lines of text pipelining.

The jolly of inconsistent workflows.

Different SQL format stylings... Makes fun when single line string replace needs to be extended to multiline RegEx handling. Or matching SQL comment configuration..

Different line endings. MacOS, Windows, Unix, Bukkake.

Different charsets / collations. Anyone wants latin1_swedish_ci... utf8... utf16... :/

Realizing some people even left sensitive data inside the SQL files (e.g. API Tokens..... Yayyyyyyy).

...

Ugh. It's never a one liner. It's never easy. -.-

I hate cleaning up messy shit.

Coworker: "I'll just refactor this one messy piece of code and catch up with you later"
Me to another coworker: "We will not see him anytime soon..."

Anecdote from when I used to be an apprentice:
Setting: Small company, number of employees -> ε, direct superior is the founder and owner, no tech background

Boss: I've looked at this backup directory of the ERP /* why is he even going through that stuff?*/, it looks messy as hell, I want you to tidy that up
Me: Those are incremental backups, I can't just go and delete some of them, the application manages them by itself
Boss: Get it tidy!

sometimes you just can't deal with that messy piece of shit iptables frontend

When you're talking about how awful it is and they think you mean your desk

I have an HP stream
this thing is a McFucking™ potato (and it's HP so i can't even get inside and replace the stock parts for good ones without breaking it)

Me and my friend > trying to attach a touchscreen display module to raspberry pi.
The module has two rows of female pins like
: : : : : : : :

The pi (model: zero w) has two rows of male pins soldered to it.
One row is fine but another row is @ 90° angle to first one.

** Who the hell bent these pins **
** A glimpse at jumper wires **

Ya let's do it,

After connection,

So many wires, totally messy & ugly

But alas it works

:)

Have you ever encountered a situation like this before?

You worked in a team, made many adjustments in the codebase, and all the changes you've made are the best practice (after some research or asking the community).

But the team leader decided to go with the "messy" version of the code and the team leader does adjust the principle of "bad code" in favour of your coworker, just because he/she is a friend of the team leader.

So, whatever you adjust or contribute is simply nullified but any adjustments made by your coworker are considered "new updates".

The fuck is up with venv, conda, pip, pip3, python3, CRYPTOGRAPHY_OPENSSL_NO_LEGACY and "you can't install packages in docker based environments" DUDE STOP WHAT THE FUCK

How the fuck is that the scripting language of choice? It has by far the most confusing and messy runtime setup. Like it's easier to make sense of Javas version-shenanigans than this bullshit.

And then you think well what gives. Runs > python ...
"This environment is externally managed and you can go kill yourself, JUST LOOK UP PEP-666" LIKE NO YOU FUCK, JUST RUN THE FUCKING SCRIPT!

It's nice you thought about separation of versions but DOCKRR DOCKER DOCKER THERE ARE CONTAINERS WHY THE FUCK DO YOU DO SOME BULLSHIT WITH ENVS IN FOLDERS REQUIRING SOME RUNTIME BULLSHIT WHAT NO STOP WWHYYY

I think I'm a good developer. I have pretty decent debugging skills, including pulling apart disassembled x86 and other architecture code.

I'm fascinated by how things work.

But almost everything is catered for by a library. Or has already been done.

I find it enjoyable to create a library or program myself, but get disheartened when I find some library or program that is written seemingly very well, compared to my own code. And then I start to think I'm not a good developer after all.

Sort of relates to my previous rant about repeatedly rewriting code.

Applies to me doing programming as a hobby but probably affects my code at work as well... I just can't help but think my code is probably awful compared to what someone else might write.

...then I see incredibly ugly, messy, badly written code by other people and I feel better...

I suppose it is like an artist who sees amazing works but cannot paint to that standard, but is well beyond drawing stick figures with crayons.

Sounds like a trivial problem but it probably impedes my progress with a lot of things.

How is coupling backend + frontend as a single nextjs app a good idea? What the fuck is this?

What if you have to create new replica sets of a backend because of high load pressure? What about load balancers?? What if i want my backend to be a microservice? How do i unit test the backend if its cluttered with frontend? WTF IS THIS

WHY DID NEXTJS THINK THIS IS A GOOD IDEA AND WHY DO SO MANY DEVS LOVE THIS IDEA AND GLORIFY NEXTJS?

Nextjs seems like the type of framework that was built by a frontend web developer who just refuses to learn backend technology at all costs.

---

its been a few hours and the concept of nextjs is bending my mind rn. I thought nextjs is just another frontend framework. A react killer. Only to find out its both a backend + frontend framework.

Cluttering backend stuff into frontend is gonna get messy no matter how much you try to modularize the code. Am i lost or am i right???

---

Scratching my head over nextjs. Looks like a great framework for small-mid project but definitely not large project. The more shit the project needs the more messy shit become. Angular has modularized all of this in separate folders -- components services guards interceptors (now new stuff coming called Signals) etc. All of it is separated in individual folders and kept frontend-only. Simple enough. No backend clutter

---

Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?

Am i insane here

Hey guys, quick question regarding employers and stuff.

I'm 14 and I've been learning and making things in PHP for around 1 and a half years now. I quite like PHP as, despite the code being quite messy sometimes, it's super easy to learn, and has plenty of features for any use case. My biggest concern is that, when I end up getting a job, whilst 5 and a half years of experience using the language is good, do you guys think PHP will still be in-demand, or should I look towards learning a new stack? Perhaps I should use Ruby on Rails, or Express - React and Redux, or maybe Django? With so many options available for developers, I'm finding it difficult to choose a stack that will stay in-demand in the future. Could anyone help me out with this? Thanks.

Edit: I've been learning Laravel, too.

We recently hired a new developer, fresh from uni. Very little real experience as I can see.
Unfortunately I weren't available for the interviews, so they chose a dev without me.

All his code is messy, over complicated and uses symfony framework for _everything_
He can't do shit outside of it.

He was tasked to find and replace some links in a few hundred excel documents, he spent ages trying to parse the xlsx documents and the replace the links and write to the document. Spent all day on it, with no results. Even though I often asked him how he was getting on, he said all was fine.

End of day, I get a tad furious, whip out my terminal and do the whole task in 10 minutes with basic bash

@dfox
There's one thing I hate about devrant...
While I'm browsing posts I can't check back for my posts or exit the app or I'll have to scroll down again (gets messy after like 50)
That means I just stop watching for the rest of the day.
Suggestions:
3rd button to mark as seen and don't show on post lists
Add a mark on last seen post so it will continue there when we return to browsing.
Thank you for this community once again

When I face with messy code and I cannot understand it for days.

No Python. I don't want your fucking eggs. Who even decided on that name??? Eggs break and get all messy, the stuff inside grows out of control or is dead to begin with. WTF!!! I feel filthy whenever I see an egg-info. EEWW

The feeling when you write a long messy algorithm and you think to yourself "this is never going to work" but then it runs exactly as you intended first try! 😎

When do you know something is being overdesigned or overengineered?

The applications that the other programmer started building are killing me. He's using Clean Architecture and it has like a million different classes and shit. It's not messy or anything, but fuck it's overwhelming.

Just to figure out wtf was happening when getting the currently signed in user's email, I had to go through like 30 folder and files. Maybe more. All files were fairly simple on their own, but the entire flow was mindfucking me. Use cases, schemas, gateways, repositories, entities, models, etc etc

And that's the client facing application, I haven't checked the API yet, though it seems like that one is simpler.

The worrying aspect here is, any time anyone else has to mess with this, they'll also have to deal with this shit. This needs some really good documentation.

My fights with other devs always revolve around the position of curly braces:

Should they be on the same line or should they have a whole line just for themselves?

I mean, if they go on the same line you have less lines of code and you can fit more into the same view, but putting them on a new line makes it all a little less messy

That feeling when you have a messy merge, nothing works but don't give a shit and go home for the weekend, that's Monday guy's problem!

I hate android studio. No wait i love it. No i hate it. Can't seem to make up my mind about it. Its slow, kills my computers performance, messy interface. But despite that it's something appealing about it. Everything seems to be avaliable for previewing as one work.. aaand then it breaks my computer and I hate it again..

We are all about structures, clean code and many other things that make our life easier, right?

Well... It's not all white and black...

As talked many times, projects can be rushed... Client budgets can be low at the start and only then grow...

Let me take an example:

Client X needs a tool that helps his team perform jobs faster. They have a $500 budget. So... Testing, clean architecture and so on - are not really a viable option. Instead, you just make it work and perform that task as needed. So the code has minimal patterns, minimal code structure, a lot of repetitive parts and so on.

Now... Imagine that 3 months pass by without any notice and clients are ultra happy with the product. They want more things to be automated. They contact developers and ask for more things. This time they have a bigger budget but short timeframe.

So once again, you ignore all tests, structure and just make it work. No matter what. The client is happy again.

A year passes and the client realizes that their workflow changed. The app needs total refactoring. The previous developer has no time for adjustments at this point and hires a new company. They look at the code and rants spill out of their mouth along with suicidal thoughts.

So... What would you do? Would you rant about "messy project" or just fix it? Especially since people now have a bigger budget and timeframe to adapt to changes.

Would you be pissed on such a project?
Would you flame on previous devs?
Would you blame anyone for the mess?

Or would you simply get in and get the job done since the client has a "prototype" and needs a better version of it?

---

Personally, I've been in this situation A LOT. And I'm both, the old and new dev. I've built tons of crappy software to make things work for clients and after years - they come back for changes/new things. You just swallow the pill and do what is needed. Why? Well, because it's an internal system and not used by anyone outside their office. Even if it's used outside the office - prototyping is the key. They didn't know if the idea would work or be helpful in any way. Now they know and want it done correctly.

So I go on a 10day holiday and when I come back I realise the scrum master commited a whole bunch of messy code straight to develop and didn’t even bother to run lint or build or test or anything. WHYYYYY??? Everything worked before that. Why is a scrum master who doesn’t have experience in front end allowed to touch my code and commit directly to master?

I know why. Because the whole team does it all the time and they just keep breaking and fixing things over one another and all commit directly to master.

Kill me pleaseeeeeee 😭😭😭

Spent another half day learning ELK and how to programatically query and run aggregations against the data that's now collected.

So I can feed it into a testing framework for releases.

I sorta feel like I'm dragging everyone else into the light...

Like "you see what you've been missing all these years? This is how it's supposed to be these days..."

Data data data... Useful data.... This is what you can do when have structured and searchable logs rather then huge messy text files ...

We kinda feel the feature you lead was messy because even though you brought up valid use cases and we decided to postpone the development of those till the next release, the user wanted them and we pressured you to get it done in a couple of days…which lead to a slightly buggy less than perfect release…so yeah, even tho you saved our asses for secretly starting development of those extra use cases beforehand we won’t showcase it as a successful release.

- Management

Wrapping up a project, I am cleaning code to give the customer the source code. The project had lasted over a year. I joined the team a few months back and it frustrated me how messy the code was. In my previous teams, any new resource was told to stick with the rules, and eventually they became embedded in them. The case seemed opposite here. Developers who wrote clean code became lax (they made me even more pissed).

Now I have the job of getting rid of warnings, formatting issues etc and I do not say this lightly, but, there was no fear of god in anyone who worked on this codebase. The code formatting I have seen makes me wanna...

Besides assorted craft materials and PC my desk has a dual purpose crocheted rubber duck: it serves as a pin cushion and my debugging friend! I made him and he has lived there since my first year of university.
I also keep a mug from my university, scented candles, notepad and pen (for all my tech savvy-ness, quick notes are still better handwritten) and whatever crafty project I'm working on.

My desk is honestly a mess (I have to clear it ~three times a week to have any space to work on) but they say creative people have messy workstations so I take my inability to keep an orderly environment as an expression of my creativity.

My biggest influence on coding style is:
"If code make reviewer puke, code bad."

In all seriousness though, I think the biggest influence is seeing messy code and not trying to replicate that.
I think every code file, however ugly it is, tells you a story. Maybe the coder was less experienced, maybe it was written during crunch or the coder is an enterprise software engineer who has to make a factory for everything and everything is generic.
In my opinion there is no perfect code style. You do what's required and hopefully in your best ability, and, as a bonus, think of the person who has to look at your code next...

For me it's kind of hard to tell whether my code is good. I have no reviewer in the company, which brings the risk of writing code so only you understand it... but so far it has worked and I've definitely seen worse than my 1 year old files. 😄

When you are very busy and got a tight schedule but some other team complains to their boss that your changes to a shared library completely broke their work and that is a "showstopper". They say it worked before so it must be their code.

So you try to figure out what happened because you sometimes make mistakes even though you took precautions. It takes almost 3 days of your time because you dive into your commits and into their messy codebase.

Turns out the fucking thing never worked in the first place and nobody took the time to validate this. Worst thing is I found the bug with someone else even though it's not even my job to do it. I wasted my fucking time.

I swear if I was not working remote I would have started a fistfight in the office.

I need some opinions on Rx and MVVM. Its being done in iOS, but I think its fairly general programming question.

The small team I joined is using Rx (I've never used it before) and I'm trying to learn and catch up to them. Looking at the code, I think there are thousands of lines of over-engineered code that could be done so much simpler. From a non Rx point of view, I think we are following some bad practises, from an Rx point of view the guys are saying this is what Rx needs to be. I'm trying to discuss this with them, but they are shooting me down saying I just don't know enough about Rx. Maybe thats true, maybe I just don't get it, but they aren't exactly explaining it, just telling me i'm wrong and they are right. I need another set of eyes on this to see if it is just me.

One of the main points is that there are many places where network errors shouldn't complete the observable (i.e. can't call onError), I understand this concept. I read a response from the RxSwift maintainers that said the way to handle this was to wrap your response type in a class with a generic type (e.g. Result<T>) that contained a property to denote a success or error and maybe an error message. This way errors (such as incorrect password) won't cause it to complete, everything goes through onNext and users can retry / go again, makes sense.

The guys are saying that this breaks Rx principals and MVVM. Instead we need separate observables for every type of response. So we have viewModels that contain:

- isSuccessObservable
- isErrorObservable
- isLoadingObservable
- isRefreshingObservable
- etc. (some have close to 10 different observables)

To me this is overkill to have so many streams all frequently only ever delivering 1 or none messages. I would have aimed for 1 observable, that returns an object holding properties for each of these things, and sending several messages. Is that not what streams are suppose to do? Then the local code can use filters as part of the subscriptions. The major benefit of having 1 is that it becomes easier to make it generic and abstract away, which brings us to point 2.

Currently, due to each viewModel having different numbers of observables and methods of different names (but effectively doing the same thing) the guys create a new custom protocol (equivalent of a java interface) for each viewModel with its N observables. The viewModel creates local variables of PublishSubject, BehavorSubject, Driver etc. Then it implements the procotol / interface and casts all the local's back as observables. e.g.

protocol CarViewModelType {
isSuccessObservable: Observable<Car>
isErrorObservable: Observable<String>
isLoadingObservable: Observable<Void>
}

class CarViewModel {
isSuccessSubject: PublishSubject<Car>
isErrorSubject: PublishSubject<String>
isLoadingSubject: PublishSubject<Void>

// other stuff
}

extension CarViewModel: CarViewModelType {
isSuccessObservable {
return isSuccessSubject.asObservable()
}
isErrorObservable {
return isSuccessSubject.asObservable()
}
isLoadingObservable {
return isSuccessSubject.asObservable()
}
}

This has to be created by hand, for every viewModel, of which there is one for every screen and there is 40+ screens. This same structure is copy / pasted into every viewModel. As mentioned above I would like to make this all generic. Have a generic protocol for all viewModels to define 1 Observable, 1 local variable of generic type and handle the cast back automatically. The method to trigger all the business logic could also have its name standardised ("load", "fetch", "processData" etc.). Maybe we could also figure out a few other bits too. This would remove a lot of code, as well as making the code more readable (less messy), and make unit testing much easier. While it could never do everything automatically we could test the basic responses of each viewModel and have at least some testing done by default and not have everything be very boilerplate-y and copy / paste nature.

The guys think that subscribing to isSuccess and / or isError is perfect Rx + MVVM. But for some reason subscribing to status.filter(success) or status.filter(!success) is a sin of unimaginable proportions. Also the idea of multiple buttons and events all "reacting" to the same method named e.g. "load", is bad Rx (why if they all need to do the same thing?)

My thoughts on this are:

- To me its indentical in meaning and architecture, one way is just significantly less code.
- Lets say I agree its not textbook, is it not worth bending the rules to reduce code.
- We are already breaking the rules of MVVM to introduce coordinators (which I hate, as they are adding even more unnecessary code), so why is breaking it to reduce code such a no no.

Any thoughts on the above? Am I way off the mark or is this classic Rx?

Someone wanted to take a look to kde on Ubuntu 18.04 in my laptop, so did:

`sudo tasksel install kubuntu-desktop`

After rebooting and all did:

`sudo tasksell remove kubuntu-desktop`

and now I don't have GUI. The problem is that I can't also have network, neither by WiFi or ethernet. So I can't install packages.

The best way to fix that is to reinstall Ubuntu? Or there is a way to recover the ability to connect to network?

BTW, yes: "someone" was myself.
Shame on me 😔

devRant can use an update where the notifications get split into comments and +1s because I do like replying to comments but they're scattered in between +1s just too messy

Starting to migrate apps from a messy structure to docker containers. Have not worked a lot with docker before so i'll hope it goes as smooth as people told me

Have been pissed at the guy who wrote the js on the project im working on (its just so messy!). Same project has python scripts I need to look at to squash a bug, and this. code. is. so. clean. They should have let this guy write everything in python. Im ashamed I ever hated on him.

Just landed my first "real" software engineering job! Now let me venture the land of messy and convoluted codebase.

So my manager mentioned off hand that we might look at updating our company website to look a little more modern...

Me being me jumped right into action and now that I've finished I remember why I haven't built my personal site.. Fuck static web pages man...

Don't know why I did this, not even happy with it but I think it'll do, CSS and HTML is messy but fuck it, it works...

How do you guy (think of) prototype UI?

I have used the pen and paper approach but when you add the interactions such as clicks and animation on the paper,it become messy.

I feel that coding up a full blown front end for prototyping is overkill. Because when you want to prototype the list , you also need to insert the dummy data in order for you see probably clicks and drag animation.

Trying to understand other people's messy code when you're sick 😖

I want a simple solide orange color for my text.In preview mode it works perfectly .when I render my composition I get this messy color any ideas ?

Ugh... some people...

Just left the office early because of the toxic climate. That one infamous collegue is basically unable to communicate without being a narcissistic 5-year-old and was arguing whether we should write a test (I was going to write the test) that would need a single additional branch in the build system.

(The test was for a parser and it should test whether it can handle absolute paths. A simple regression test with a file and an expected output. Because absolute paths are different for every platform and user, the files to be parsed would have to be generated with appropriate paths before the tests were run. Well that would require one single python script and a single line in the script that runs the script and DONE)

Well that guy was unable to focus on his own work and started an argument about whether that test was necessary.
Even though I still think it is necessary, it might have been a reasonable argument if he would have acted more agreeable. But he was saying the feature was useless anyways "everyone will use relative paths only anyways" and "because noone here cares a ratass about maintaining the tests it will all fall on me again" ..

Wtf was this guys problem, I (CAPS) was going to write the stupid test and since when do we not write tests in order to better maintain our product? I get that he worries that the test environment will get more messy, but thats better than having the product code go messy or unfunctional! And c'mon guys, how are absolute paths a redundant feature...

If there's one thing I'd gladly kill with fire, then pass it over a steamy steamroller, then burn it a tank of hot fluoroantimonic acid, is every fucking Java library that returns null instead of throwing a meaningful exception.
Is it really that difficult for you to throw an exception anyway, then let ME figure out if I can ignore it or not?
Thanks to you, now I have to do super messy reflection things just to figure why did you return a null.
I'm not your fucking psychologist trying to pull your inner secrets. But I have to be, for the sake of stability of my app. Which already has its own mess of problems on its own.

Me and the lead developer of my team gave a long and detailed explanation to our manager entailing the current state of a budge program our workplace uses.

This app has been bugging him for a while, he did not write it and has not been given an opportunity to rewrite the damned thing. Its a really...really messy application, and whilst it is a functional one it most certainly is NOT an efficient one since adding or moving things only incites more spaghetti mess.

We were laughing while giving our report, but both of us were crying inside. The main thing is, we both love PHP and the things he has built are very well structured and efficient, he has good technique, but will admit at certain caveats regarding the way he structures his dbs stating that he always has to do changes, which hey, its the nature of the beast, dbs change all the time. But our issue with php is the same: it lets beginners write monstruosities that are harder to do in other environments.

It really is a permissive language. But I reckon thay such lax nature is better left at the hands of the more experieced developers that know what they are doing.

Either way, we will restructure this motherfucker taking advantage of the new standards (which both of us are well versed in) and applying a more structured approach with a nice frontend interface (we be looking at Vue.js and React although we are considering Angular as well)

Gon be some good times.

I reported to our team leader (who is not a developer) that me and my colleague has been having problems with our senior developer whose codes are unmaintainable and messy. I told the team lead that I am losing my trust towards my senior developer and that his codes are messy and not following the coding standards. I was nervous at first because this certain team leader is tight with the senior dev. But still, I expected the team lead to be objective.

I was surprised because the team lead asked me if 'I was perfect' and then the team lead continued to shift the conversation towards me. Team lead then started to compare me with the senior dev which is unfair because I've only been working for 2 years whereas the senior developer has been doing this for 6+ years. Team lead said that I was arrogant. Team lead sent our convo to the other teammates and friends. Team lead told me that I am such a baby.

Fast forward, the senior dev talked to me. Told me that he was busy so he didn't get to improve his codes. Which I dont buy because I often see his discord status as playing during work hours. Told me that it wasnt him. Which I dont know if i should believe since he always lies. Told me that his knowledge is outdated. Told me that maybe because I came from a good university and he did not. He apologized and told me he will improve. Sounds good right?

It's a lie. Because then my friend gave me a recording of his voice ranting about me after our talk. In that recording, he said that I have nothing to prove so I dont get a say. He said that he doesnt care about me. He said that I am cocky. Which I dont understand. I only commented abt his work, why is he attacking me personally? Plus, if someone new like me already already noticed the flaws in his work, what does that say about his skill?

My teammates then asked me to just take the fall lol take note that these teammates were also complaining about this senior dev. they asked me to just give them what they wanted to hear. That I am the one who's wrong and the bosses are right. I said I wanted to defend myself but they hated me for that. They told me to think about what would happen to them. They told me I am selfish. Is it selfish for wanting to defend myself?

I defended myself. I told the senior dev that my intentions are for the right reason. He told me he understands. Later that day, a friend told me he talked behind my back again.

Senior dev told me that the team leader cried because of the words I said. Which i found confusing because it was my own feeling, my own opinion that i am losing trust with this certain senior dev so why would the team lead be so affected by that? Also, i showed our convo to the most objective people i know and they said that i didnt say anything that is offensive nor arrogant I have no control as to how people would react to the words I say. It's beyond me.

I feel so helpless. I told those things to the team lead because I think a team should be open to each other but I was blown out of proportion instead. My friend told me that the team lead and the senior dev are still talking behind my back.

If they do this every time someone tries to speak up, will they ever grow?

You know you should tidy up some space when your ssd has more space left then your hard drive

I still have a second hard drive, but I'm too lazy to move either my steam games or my programs over there...
The time will hit me when the last GB has been used