there is a dev in our company who actually does this:

if()
{
}

and not this:

if(){
}

This is unreal.

You know what I mean

200 OK
{ ok: false, error: "Not found", code: 404 }

Hello bronchitis, my old friend
I've come to cough with you again

Fiddling with the UiPath RPA tool. What the fuck is this monster?

So, you create apps by drawing a flowchart, like some kid using Scratch. Then, suddenly, you have to create a .NET object just to get a random number!

Who the fuck is the target audience that can create objects, call a directory read function, etc, but can't write a loop?! Show me that fucking person.

Then I have to debug the fucking selectors when they don't work correct. All this requires is understanding how UIs are structured under the hood. So, you know that a menu bar is a window, but you need to draw a fucking if statement?!

And how would you debug and manage this monstrosity?

It like we learned nothing from all the Excel apps we build for decades.

I mean, it's an impressive app. But, why does it exist?

Someone needs to stop this before it gets out into the wild or we'll all be debugging flowchart a created by business analysts.

You have been warned. Join the fight or accept the consequences.

The quality of my code and how often people reuse may be directly correlated to how shit it is.

//////

Client: We are completely unable to plan a construction project successfully. We want you to use AI to do all of our project planning for us. Our requirements are that instead of needing to spend any money or time planning we just want to press a button and have a computer instantly put together all of our project plans for us. The program also needs to identify optimizations on it’s own and change all related plans enterprise-wide. All copies of the plans should be able to be kept up to date at all times so we’re never looking at an old plan again. We also want the ability to print.

Dev: …

This seems accurate.

Kubernetes for Beginners

The default value... 😂😂😂

8 months into a complex Agile project, managing multiple Scrum teams -
I still feel it would go much faster if I just do it myself.

I was hired as Project Manager.

After few days, I discovered that:
- I didn't have a team
- I was also the main and only developer
- all the projects I was assigned to were late
- I was also the account manager and I had to explain the delay to the customers.

And no, the salary didn't make up for the daily loss of reputation.

I lasted more than I thought, when I discovered that customers were not interested in delivery either, as it was a kind of money laundering scheme

To be a good developer, you must thrive in chaos, and have an insatiable desire to turn it into order.

All user input, both work tasks and actual application input, is pure fucking chaos.

The only way to turn that input into anything usable, is to interpret, structure and categorize it, to describe the rules for transformation as adequately as you can.

Sometimes companies create semi-helpful roles to assist you with this process. Often, these people are so unaware of the delicacy of the existing chaos, that any decision they make just ripples out in waves leaving nearly irreparable confusion and destruction in its path.

So applications themselves also slowly wear down into chaos under pressure of chaotic steak-holders which never seem to be able to choose between peppercorn or bernaise sauce for their steaks.

Features are added, data is migrated between formats, rules become unclear. Is ketchup even fucking valid, as a steak sauce?

The only way to preserve an application long term, is refactoring chaos into order.

But... the ocean of chaos will never end.

You must learn to swim in it.

All you can hope to do is create little pools of clarity where new creative ideas can freely spawn.

Ideas which will no doubt end up polluting their own environment, but that's a problem for tomorrow.

So you must learn to deal with the infinite stream of perplexed reactions from those who can't attach screenshots to issue reports.

You must deflect dragging conversations from those who never quite manage to translate gut feeling into rational sentences.

You must learn to deal with the fact that in reality there are no true microservice backends. There are no clean React frontends. There are no normalized databases. Full test coverage, well-executed retrospectives, finished sprints -- they are all as real as spherical cows in a vacuum.

There is no such thing as clean code.

There is only "relatively cleaner code", and even then there are arguments as to why it would be "subjectively relatively cleaner code".

Every repository, every product, every team and every company is an amalgamation of half-implemented ideals, well-intended tug of war games, and brilliantly shattered dreams.

You will encounter fragmented shards of perfect APIs, miles of tangled barbed documentation, beheaded validator classes, bloody mangled corpses of analytical dashboards, crumbled concrete databases.

You must be able to breathe in those thick toxic clouds of rotting technical and procedural debt, look at your reflection in the locker room mirror while you struggle yourself into a hazmat suit, and think:

"Fuck yes, I was born for this job".

To my ex manager

you left to berlin, and left me to rot

my new lead sucks, i kid you not

it was ok if I slacked off, You used to be chill

But my new lead is uptight, he's on my list to kill

I wanna run errands in work hours, is that so bad?

was doing so for years, now i lost what i had

I cant drive in peace, coz i know he'd call

so i had to cancel plans to go to the mall

its like 10 to 6 is now constant work

I hate my new lead, he is such a jerk

I wonder who is the imposter then

Finally pushed myself to complete readme and release the docker image most of our websites use.
For anyone interested, the image is open-source and available on Github, feel free to use it or suggest any improvements :)
https://github.com/Eworkssk/...

That's a unique skill

Wanna mess with users? Take

“OK” and “Cancel”.

You know what looks visually the same but means the opposite?

“NO” and “Confirm”.

Deploy that little ui update overnight and watch the world burn.

Learnt the hard way

NEVER WRITE THE UI BEFORE WRITING THE BUSINESS LOGIC

😮 Aparently double tapping a rant does a ++.

Try it if you are on mobile! 📱

java ...

Out top management has made the decision that our managers must have billable work as well on projects. I feel like winter is coming.

Daghhhhhhhh Kafka.

Set it up, seems to work fine.

Oh no...! Take a broker down, then messages go missing - hmm, that's not right. Fine, I'll just look into... Ah, bad replication factor, my fault. So then it's all fixed! Woop. Wait, no. Some messages still going missing occasionally. Oh, only set to "at most once" delivery. My bad, fix that, and... now everything is out of order. Oh, ok, partitions setup wrongly. Wtf, now the whole thing stalls when there's a network blip until a restart. Right, ok, looks like commits have to receive acks in the library I'm using before continuing. Switch to a library that uses CommitWithoutReply. Brilliant....

Apart from said library seems to have commits failing all over the place because it keeps trying to commit during a rebalance 🙄😒😤

The frustrating thing is I KNOW for a fact that Kafka is a fault tolerant, resilient, horizontally scalable thing capable of handling stupid amounts more than I'm throwing at it without missing a beat. But damn,configuring it, and checking you've configured it sanely is a royal, monumental PITA.

job posting must be difficult in latin.

Found this somewhere and started crying

Tell me and I forget. Teach me and I remember. Involve me and I learn.

I can lead other people to treasure i cant get😅

Why do we need a backend?

Code review titles by year:

1990 - your code is using to much memory
1995 - your code is not running on window 95
2000 - your code is slow
2003 - your code don't have tests
2005 - your code is not 64 bit
2009 - your code is not using mvc patters
2010 - your code is not horizontal scalable
2011 - your code should be written in js
2015 - your code is not mobile ready
2020 - your code is racist