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".

Holiday was gud 🤩 Now some rest and work tomorrow 😴 If anyone wants some good steaks for dinner, I could put my calves up on ebay for a nice price 🤣

Ah, another day, another regression found in a major library

guess i work for all these companies as a volunteer

🤦‍♂️

good thing i'm no where near their 6 figure salaries either.

maybe i should get that 6 figure salary and then eat more salads and steaks at the free food court, type more shitty code on couches, and play more foosball during my approximate 4 hour work day to acheive their software levels

if only i was so good

Well I've finally quit Snapchat steaks. I've kept up with it for a couple years but I'm finally quitting. Also I just wanna say. Fuck Snapchat and its terrible android implementation.

ah yes this life.
the life of a persons stuck temporarily in a dirty town with only yawning oblivion before and behind even if he does what he should and significantly reduces his income in the process and therefore the wine and steaks stop. sigh.
thats worked so well for all of them health wise. heh