These clowns make my blood boil.

fullStackClown: Hey I need some info on that specific color you want for this design

managerClowns: Yes it should look like this <<sends screenshot>>

fullStackClown: That is not a color, it is a screenshot

managerClowns: Yes it should look like this

fullStackClown: Do you know what hex code that is for that color? Can you ask the design team what color from our corporate identity they used?

managerClowns: Yes it should look like this

fullStackClown: Not helping... okay fine I used the eyedropper and I see the hex code is not used anywhere else in our app, so what color should I use?

managerClowns: Yes it should look like this

fullStackClown: ...

Manager: Messages not visible! bug ticket!!!!

Dev: oh fuck, there's an issue with our chat system, not good! _inspects ticket_ oh, it's just a display issue that actually is according to the previous spec, yawn...

Dev: please describe the bug better next time, I though we had a major outage, this is simply a small design issue...

Manager: ...

Dev: ...

I think I'm quitting soon guys. I literally do not get paid enough to deal with these incompetent idiots each day.

Meanwhile:

Management: forget your shitty salary, take one for the team, you get 3% of the shares in the company!!!!

Dev: what fucking shares, you haven't even converted to a corporation yet, THERE ARE NO SHARES

Management: ...

Dev: ...

Oh yeah and they called me at 6:30 PM today: "so i guess you are winding down for the day"

fuck outta here i haven't been working since 5 you fucks

jesus i swear some people need to screw their fucking head on straight, so far gone into the hUsTlE CuLtUrE they don't even know what reality is anymore

In the Ruhr area (Germany) we have some very old, very strange words with strange meanings. One of those words is ‚Prutscher‘.
A Prutscher refers to a person who does things but never gets a good result, due to lack of knowledge or simple carelessness. Most of the time, Prutschers are people who are interested in certain subjects and often work in the related jobs, but who lack the motivation to properly train themselves, learn what there is to learn and to always keep up with their technologies .
Here are a few examples I've stumbled upon so far in my career:

- Developers in their 60's who read a book about PHP 25 years ago and decided to become a software developer. Since then haven't read anything about it. Who then now build huge spaghetti monoliths for large companies, in which they prefix every function, every variable and constant with their initials and, of course, use Hungarian notation.

- People who read half a fucking tutorial about <insert any fancy js framework here> and start blogging/tweeting about it

- Senior web developers who need to be told what the fuck CORS is and who can't even recognize CORS related errors in their browser console.

- People who have done nothing else for 18 years than building websites for companies on Wordpress 1.x and writing few lines of PHP and Javascript from time to time. Those who are now applying as a frontend dev due to the difficult economic situation and are surprised that they are not accepted due to a lack of experience.

- Developers who are the only ones working on Windows in the team and ask their Linux colleagues for help when Windows starts bitchin.

- People who have been coding for 30 years, have worked with ~42 languages ​​and don't know the difference between compiled and interpreted languages ​​in the job interview.

- Chief developers at a large newsletter-publisher who think it's a good idea to build your own CMS (due to a lack of good existing ones, of course).

- Developers who have been writing PHP applications for multinational corporations for 25 years and cannot explain how PHP is executed. They don't even know what the fucking OPcache is, let alone fpm. FML

- People who call themselves professional developers but never ever heard of DRY, KISS, boy-scout rule, 12-Factor App, SOLID, Clean Code, Design Patterns, ...

- Senior developers wondering why the bash script won't run on their fucking Windows machine.

- Developers who consider Typescript to be a hindrance and see no value in it.

- Developers using ftp for deployments in 2022

- Senior Javascript Developer applying for a job and for whom Integer is a primitive data type in JS.

- Developers who prefer to code without frameworks and libraries because they are only an unnecessary burden/overhead and you can quickly code everything up yourself.

- Developers who think configuring their server(s) manually is a good idea.

You fucking Prutscher. What you have already cost me in terms of work and nerves. I can't even put it into words how deeply I despise you. I have more respect for the chewing gum that has been stuck in my damn trash can for the past 3 years than I do for you guys. You are the disgrace of our profession. I will haunt you in your dreams and prefix every fucking synapse of your brain with MY initials.

As a well-known german band once sang in a very fitting song: I wouldn't even piss on you if you were on fire.

If you recognized yourself in one of the examples here: FUCK YOU!

One of the guys in my uni group project accused me of bullying, shutting him out of the group, ignoring him and taking over his work. He complained to head of year, I had to have a "discussion" with head of year, welfare tutor and my personal tutor.

For supporting evidence, I brought the message he'd posted in our team Facebook group where he told me to do the thing I was doing. The discussion didn't last long, but it seemed he was unhappy with me asking questions, mean things like "I need a draft api to do my work, why don't we sit down and design it instead of the UI you're working on?"

Conclusion? He "worked on a separate project". Got to the end of the year, the whole class went for pub drinks, someone else came up to me, had been through the exact same thing, exact same person, different group project.

Group projects teach you to hate people.

brain storming about system design on miro board

at the beginning, all devs add components they think that might be relevant for the system.

PM heavily moves everything around, deletes or changes meaning of added boxes without asking. after five minutes, he is the only one using the board, rest of the team is just watching.
PM: come on, guys. don't just sit and watch, you can also participate.

besides that, the resulting system in the end was complete garbage.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

A story about burnout you say? Well, here it goes.

In 2019, I worked in a now-defunct startup. Back then, I was deep in "treatment" with wrong medications that almost ended up turning me into a vegetable. When I was hired, my mind was already deteriorating quickly, and I was caught in a downward spiral of losing intelligence.

Prior to working there, there was never ever ever a situation in my career when I was given a problem to solve and failed to do it.

But right then, with already double-digit IQ and constant, pumping anxiety, I was seeing task descriptions that looked familiar and doable, yet I absolutely could not do them. I couldn't comprehend. It was an absolutely screeching, crippling panic about me losing my intelligence forever, being fired and ending up unhireable, dying alone on the streets.

Apart from my depression I recovered from, this very experience was a trauma that haunts me to this day, every day. You know, my experience being raped as an adolescent doesn't, but this, it's something else. Now, my intelligence is back, I design architecture, I'm a CTO, and my solutions are objectively cleaner and better in every way than what I did pre-depression. Yet, I still feel a sharp, sudden rush of anxiety, and my heart skips a beat, when I think about writing code or even opening the IDE.

I don't know how does one recover from this. I'm now slowly transitioning into "architecting CTO" role that is just being a devrel, assessing ethics, working with business to realize their need, designing solutions and leaving the implementation for the team to do. You know, the stuff I was taught in the uni.

Maybe doing open source and launching small pet projects will help. But at this stage of my life I have no emotional resource to care.

Everything about the company is a mess. The only thing that is decent is the people. And by that I mean they aren't shit.
Workflows are fucked.
Clients are fucked. You're pressuring me to get this shit production ready before new year's eve and you still don't know what the text should say and want to make changes to the UI? The fuck?!
Design is a complete shit show. There is a design team. They only make a fucking psd to show clients how an interface would look like. No mobile version (but it's still expected to work!), no markup. Resolution is fucking inconsistent and whenever a change is requested, they are nowhere to be seen so I have to actually do designing on top of having to use this worthless fucking framework I hate it so much.
Codebases are turbo-fucked because of said framework.
Databases are an inconsistent, fucked up mess. No foreign key constraints because every single fucking table is using the MyISAM engine.

And the thing that really makes me incredibly angry is all the "custom systems" look the fucking same at the database level. Like 30 fucking useless tables made for stupid HR workflows that make no fucking sense.

Ah the classic "Grau Dunkel 70". I know exactly what hex code that is. Thanks, design team!

Fuck you.

long time listener, first time caller. I love designers. seriously. I love getting a nice juicy Figma file and not knowing how the heck I'm going to do half the wild stuff in it, but it's beautiful, so I'll figure it out. Go ahead, send it to the client. But designers who learn how to use something like Elementor or one of those crappy kitchen-sink themes, call themselves developers, and win work with clients I share with them. I'm the one fixing everything when that crap breaks. I would never in a million years present myself as a designer, even though I know I know a damn sight more about design than they do about dev. I get it, everyone needs to make a buck, but every time this happens it makes me sick to my stomach. We're on the same team. I always, ALWAYS, go to the mat for good design. Why don't more designers have an equal amount of respect for us? Design phase always goes over deadlines and we always have to pick up the slack to make the hard launch date. Well, now I'm just rambling.

Another day of the incompetent design team wasting my time

#clowndesigneddevelopment

Once again, due to poor management, I find myself exporting svgs from Figma, saving them as pngs, and importing them into our application... (remember I'm a developer, NOT a designer)

Don't we have a design team who can export the needed assets for a feature?

"Noooooo fullstackclown can do all of that himself! He's an expert!!!"

The fucks are lucky I dabble in digital art as a hobby and even know how to do this stuff...

FML

Oh, as a noob dev my team was using a dropdown library for our filters in the website. The code was messed up cause they kept changing the design halfway through dev and after releases and then finally after some releases, the client wanted multilevel options as a new requirement.
So I scrapped the whole thing and made my own multilevel dropdown component (there were no decent libraries then) and we used that from then on. It has many issues now that I look back (who cares about keyboard interaction right?). But that is a refactor for another day.

My manager’s manager (my superboss)..

Every time we go for a design discussion, this guy goes into his own world of inspiration, motivation, religion and damn things.. the more you think of pulling him back, the more lame jokes he starts to crack, the more you’ll bring in work related talks, the more stupid his output will be.. it is now resulting in a late delivery date, a frustrated manager, and a frustrated team. Moreover he says, he’s inspired from Elon Musk, dafuq, I mean seriously? What part of his approach on productivity you actually got inspired by? Sleep?

HP makes shit devices. How the fuck you gonna regress with product design from 7 years ago?

Like whos the fucktard that thinks “how about in order to swap a keyboard, we make the user take EVERYTHING out and then put it into a new upper housing?”

Or my favorite is “instead of screwing a screen panel in, lets use some painfully difficult to access stretch tape?”

Fuck HP’s product design team. If by some off chance any of yall know anyone who’s part of that team, tell them i said they can eat a fat dick and get aids.

Apple Developer webportal(s). My god, how on earth do you manage to make navigating and managing iOS projects so bad.

I mean seriously, for a company that makes some of the best UX experiences, and has the most design focussed thinking in the world, this has to single handedly be the worst god gam experience ever.

I mean, did your xcode IDE team have nothing to do so you let them make this pile of fucking trash.

So I work at a big IT company. Keep in mind you could say I'm lucky to be here my last job was as a mechanic. So they put me on this team filled with the most draining kunts I've ever seen.

I have been here for about a year and I am yet to be put on a project, so im just training. They asked me to get certified to be on a project which is complete bullshit because every other fuckwit is on a project and noone is certified.

ONTOP of this, there's no work to be done anyway, yet they keep hiring fucking Grads. LIKE FUCK OFF, get work for the rest of us first you fucking IDIOTS.

Anyway, the cert is the driest fucking content, like kill me now, I try to read about it and I just want to blow my fucking brains out.

Like is IT all like this? I used to work at a web design company and that shit was fucking fun, but paid like $2 an hour the cheap fucks.

Anyway that's my rant, I'm sitting my exam tomorrow for this cert and honestly, I don't even know why. I literally know ZERO. fucking going in to guess this shit. would rather go down to bunnings buy the coarsest piece of rope and just dangle like a fat dick.

Anyway cheers lads. have a great day

F@#!k my year,

After a year long Mobile app project finally shipped where I served **two lead roles (UX design and mobile dev)**; I had my status meeting with my manager to discuss my next phase of my career. To which I was told I would be promoted to Chief or partner level at my workplace, if shipped on time, which we did.

The response I got was unsettling, I've been asked to "step down" from my architect role and join our innovation sales team since it was discovered I also have an MBA. So much so my skip level manager cut off all my dev licenses week of release. 🤣

The overall need was for me to oversee H1B and contractor resources moving forward on new engagements, as I was now "too expensive". I like coding, but it doesn't sit well with me at all...

2 Items in Rant: Technical Lead -> Development Manager, and Boss giving me his administrative work.

1. For the last few years I've had the role of a Development Manager. I've always been very hands on and even when going from a Technical Lead to a DM I was pretty active in the code: not coding every single day but still got into it, shifted towards design and architecture type things, etc. For the most part I've enjoyed it, but with each passing year (4 years now) I feel like my boss is pusing me further and further away from being Technical. Like now he's got me making some spreadsheet because he's too lazy to do it himself.

2. Few weeks ago it was setting up meetings for him, basically turning me more and more into his glorified administrative assistant. I know Senior Leadership is so goddamn busy they can't setup their own meetings, but come on. Half the time he's ranting to me about someone and telling me to tell this person this or that. I got a suggestion: you could try telling them yourself?

I feel like if I stay at this company much longer I'm going to lose all of my technical skills and continue to get taken advantage of by my boss and the rest of the senior leadership team who couldn't talk technical and code talk if it bit them in the ass.

So we 3 devs working on a real estate system.... The guy who initially wrote the system wrote it in a fucked up state
Project structure was shit so we had a meeting and I suggested we restructure the project and also have some minimal documentation coz the system is growing we adding more features before current ones are finished

We agreed and started polishing up the system coz it seemed more features we wanted were now becoming more and more difficult to implement

So the other guy tells me to pull some updates.... To my surprise he had started documenting the system without restructuring first.... Had to quickly restructure the thing and push updates
How can 1 start documenting the very same design we want to abandon 🤦

Best:
Seeing ALL the members of my team finally coming into their own. One person tackled our entire not-at-all-simple CI/CD setup from scratch knowing nothing about any of it and, while not without bumps in the road, did an excellent job overall (and then did the same for some other projects since he found himself being the SME). Two of my more junior people took on some difficult tasks that required them to design and build some tricky features from the ground-up, rather than me giving them a ton of guidance, design and even a start on the basic code early on (I just gave them some general descriptions of what I was looking for and then let them run with it). Again, not without some hiccups, but they ultimately delivered and learned a lot in the process and, I think, gained a new sense of self-confidence, which to me is the real win. And my other person handled some tricky high-level stuff that got him deep in the weeds of all the corporate procedures I'd normally shield them all from and did very well with it (and like the other person, wound up being an SME and doing it for some other projects after that). It took a while to get here, but I finally feel like I don't need to do all the really difficult stuff myself, I can count on them now, and they, I think, no longer feel like they're in over their heads if I throw something difficult at them.

Worst:
A few critical bugs slipped into production this year, with a few requiring some after-hours heroics to deal with (and, unfortunately, due to the timing, it all fell on me). Of course, that just tells us that next year we really need to focus on more robust automated testing (though, in reality, at least one of the issues almost certainly would not - COULD NOT - have been caught before-hand anyway, and that's probably true for more than just one of them). We had avoided major issues the previous three years we've been live, so this was unusual. Then again, it's in a way a symptom of success because with more users and more usage, both of which exploded this year, typically does come more issues discovered, so I guess it tempers the bad just a little bit.

I’ve been interviewing at a few companies lately. I’m a dev with ~6 years of experience with a specific language. Most of the experience comes from working in companies that developed their own software, not talking about cms stuff. Analytical, data tracking systems. Now working at a fintech. I’ve got an offer to work as a senior developer in a smaller tech team, with more salary. I’ve approached the current company about the offer and they told me that they don’t think I’m a senior dev and rather a strong mid level dev. The Hr also told me to think about if I’m really a senior and if the other companies expectations would be met. They would increase my salary, but not quite match it. It’s not too far off though. Their reasoning for this was that you need a lot of experience with their product (which does not correlate with seniorness of a developer, only the worth of specific employees for a company IMHO) and system architecture design. The problem is that we don’t see any tasks that could implement any system design for as log as I’ve worked here, so I don’t see how I could work into a senior role at this company. Of course imposter syndrome kicked in and I’m triple guessing myself if I should join the other company as a senior now. How should I aproach this? The current company is stressful to work at because of big workload, a lot of my coworkers think the same thing about the workload.

Uber drunk and have to get up in 3 hours for lots of meetings hooray 😵. Anyways, my boss saved my from my hell scape of a team that I was on an now I actually feel like I can contribute. Fuck anyone who tells me how to design shit. I’m really good at making stuff good - and anyone who says different is a fucking idiot.

I work in a small team. As the senior dev I tens to focus on important tasks that shape the core of the product but some times I can’t divide my self when there are multiple tasks at hand, so I pass some tasks to the an other mid level dev.

So the task was to create an automation in order to CD (continuously deliver) an order from WHMCS of the (git versioned) product to customers UAT, PROD envs.

To get a background this is an old guy with “constricted” experience in PHP/jQuery/Joomla/Wordpress.

So when we were breaking up the tasks he told me he would like to implement this so i gave him the task as i was busy with core features.

I was like what could go wrong? I know he doesn’t know much about CI/CD but he can read right? He will google right? He will search for CI/CD solutions that do this out of the box right? He will design on paper or what ever and do small POCs right? He will design the flow first before starting the implementation right? RIGHT?

So fast forward to today I had a call with him this morning about some DB staff. And he wanted to show me his progress…

His solution is:
(parentheses is my brain)
1. Customer completes WHMCS order (perfect)
2. Web Hook 🪝 action (YES)
3. cpanel gets source and “automatic!” Init, all using pure PHP code ignoring the usage of the current framework (ok… something is missing)
4. cpanel web hooks(?) WHMCS to send email to customer with the envs initial setup page(?)
5. Customer opens link and adds setup info (ok fuck, fuck, fuck)

(Ok stay cool composed, lets ask some questions maybe he thought it all in a cool way I can’t get my mind around)

Me: So how are you gonna get the correct version from the repo to the env and init the correct schema?

Dev: I haven’t thought about it yet.

Me: Are we gonna save each version to a file system then your code is going to fetch them?

Dev: I haven’t really thought about it we will see. But look on customer init user setup I implemented a password strength validation and it also checks if the password is the same.

So after this Pokémon encounter I politely closed teams. Stood up drank some (a lot) coffee ☕️. Put out the washed laundry while reflecting on life’s good things, while listening to classical music 🎼 .

Then I sat on my office chair drank some more coffee, put some linking park starting with in that order:
“Numb” then “What I’ve Done” and ended with “In the end, it does really fucking matter”

Design team loves to use any in their components. I just love having to dig through multiple nested components to find out what i should put as input or console loging to found out the outputs. Whats the point of using typescript at that point. It costs nothing to write a single interface..