23 comments on a single PR.

Am I a nazi or a good tutor? I think so.

Oh my fucking god.

How can you, after 2 decades as a developer, still produce code to this very day that has that many warnings and suggestions that Visual Studio lights up like a bloody pinball machine from all the squiggly lines!?!

Take your craft seriously or find something else to do!

Does anyone have a good suggestion to a (PC) game that is quick to fire up, runs in a window and offers some distraction for 5-10 minutes at a time while I wait for docker builds to complete, deployments to finish etc? Just braindead shit, like Clash of Clans on mobile for instance.

Can't decide whether I like React or not. Hated it in the beginning, then sort of started liking it and even thinking it was great just to fall back to the dislike stage again where I roll my eyes and think it's a messy, crowded pile of shit that breaks with all sorts of good software principles. This has fluctuated up and down for over 3 years.

It's the only language/technology/framework I have had this experience with. Weird.

Finally fashion makes sense to me.

When will managers understand that there is a huge difference between a UX designer and a graphical designer?!

FML. The time wasted trying to explain that the proposed GUI is rubbish because they put a graphical designer in charge of planning the entire application flow..

Always try to work with people more skilled than me.

Sharepoint. 'Nuff said.

Donald Trump reminds me of the type of code I wrote back at my very first job as a developer.

It was built wrong from the ground up, required way too much resources and space, contained flaws and bugs in almost every method, spat out random and inconceivable messages in the log and threatened to blow up at any given time. But for reasons unknown it kept going, managed to fool people it wasn't as shit as it really was and the client couldn't get rid of it even if they tried.

Don't be a dev if it's just not for you.

It's not for everyone, and you should figure this out at the very early stages of your education. The ones it's not for that still persist will hate their life. And leave their job. And leave unfinished, crappy code behind for the rest of us to clean up.

Becaue you are getting paid really well to build what is essentially virtual LEGO!

Streams in Java. What a joke! That was the answer to LINQ? Come on....

Can anyone with some AWS IAM skills please shine a light on this one: I needed access to create a slack notification for a job in Code Pipeline. Simple enough, but we (devs) have next to no access to AWS so every time I try something I am stopped by the red "user X is not authorized to perform Y on resource Z.." warning message. I send an email to OPS and ask for permissions needed to do what I need (in this case: create a Slack notification for a pipeline), and I am granted that specific one. It gets me one step further, until I am stopped by a new red warning message. This has been going on for over a week, with a total of TEN new authorizations added to my user. That's TEN red warnings, TEN emails asking for access, and TEN replies saying "Ok, can you try now?". Today I finally got the god damn slack notifier set up, only to get one last red warning slapped in my face: I am not allowed to SEE the notifications configured for my pipeline. Please insert four letter word that rimes with DUCK here: [_________]!!.

I REFUSE to believe that this is how access should be granted in AWS. Can I tell my OPS person that there is somewhere they can find a list of required access rights to complete a specific operation ("Create slack notification for pipeline")? I know there are example policies for various things, but if there isn't one for what I need how should OPS go about granting me access without this totally ridiculous "try again now" approach?

Oh, and @assmaster: don't comment "nice" to this one. This is shitting me off.

Happy 25th birthday, Windows 95.

A guy that just did not know how to code. He had years and years of experience (?), but DID NOT KNOW HOW TO CODE. He was given a simple task, spent weeks on it and what came out was usually 60 lines of "if, elseif, elsif....else".

He was given several warnings, and eventually "voluntarily" left the company.

I still get screenshots of his code sent by one of my ex-colleagues who's still there when he stumbles across it.

Finally read the Steve Jobs autobiography.

That guy is going to make it big!

Just refactored 100+ lines of madness to 5 (FIVE!) lines of code. It's pleasing me and shitting me off at the same time.

Some people still get paid per line of code, I'm convinced.

CodePipeline single branch limitation. Shame on you Amazon.

Github Actions FTW.

I still use WinDirStat.

Fuck you, previous lead architect dictator! I spent a year arguing against your rigid nonsense custom built bullshit, and a year and a half after the client finally caught on and got rid of you I just got bitten yet again from one of your retarded over-complicated "solutions" to problems that never existed in the first place.

I wish I could send you an email and tell you about how I have thrown out all the useless shit you created and that we are all clearly better off now, but instead I will just share my frustration on DevRant and hope you read it and know exactly who you are.

I feel sorry for your current client.

A previous colleague of mine had plenty of years in the industry as a Java developer, but somehow still had absolutely no idea what he was doing. We used to send screenshots of his PRs to each other just to give our eye balls something to roll about - I have never seen anything like it, anywhere.

After multiple warnings of never delivering a single thing he eventually "voluntarily" left the company. He now works at a school teaching programming to students. The circle is complete.

A while ago I was agressively interrupted by a colleague while chatting to another (more sane) colleague as he overheard us merely discussing using message queues to solve some issues we were facing. I was told these decisions were not up to me and had to be "lifted to a higher level and discussed amongst the entire team".

8 months later we all receive an email where the same guy proposes the exact same solution to solve our issues.