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

Never have I been so furious whilst at work as yesterday, I am still super pissed about going back today but knowing it's only for another few weeks makes it baerable.

I have been the lead developer on a project for the last 3~ months and our CTO is the product owner. So every now and then he decides to just work on a feature he is interested in- fair enough I guess. But everything I have to go and clean up his horrendous code. Everything he writes is an absolute joke, it's like he is constantly in Hackathon mode "let's just copy and paste some code here, hardcoded shit there and forgot about separation of code- it all goes in 1 file".

So yesterday he added a application to the project and instead of reusing a shared data access layer he added an entirely new ORM, which is near identical to the existing ORM in use, for this one application.

Being anal about these things, the first thing I did was delete his shit and simply reference the shared library then refactor a little code to make it compatible.

WELL!! I certainly hit a nerve, he went crazy spamming messages on Slack demanding I revert as it broke ONE SINGLE QUERY that he hadn't checked in (he does 1 huge commit for 10 of everyone else's). I stuck to my principals and explained both ORM's are similar and that we only needed one, the second would cause a fragmented codebase for no benefit whatsoever.

The lead Dev was then forced to come and convince me to revert, again I refused and called out the shit quality of their code. The battle raged on via the public slack group and I could hear colleagues enjoying the heated debate, new users even started joining the group just to get in on mine and the cto's difference of opinion.

I even offered to fix his code for him if he were to commit it, obviously that was not taken well ;).

Once I finally got a luck at the cluster fuck of shit he had written it took me around 5 minutes to fix and I ever improved performance. Regardless he was having none of it. Still the demands to revert continued.

I left the office steaming after long discussions with the lead Dev caught in the middle.

Fortunately my day was salvages with a positive technical discussion that evening at a company with whome I had a job offer from.

I really hate burning bridges and have never left a company under bad terms but this dictator is making me look forward to breaking the news today I will be gone in 4 weeks.

FUCK Android, whoever invented this piece of shit should be really proud of themselves... And yes, this rant comes from an iOS developer who's working on a project in react-native... Why the fuck everything should always work on iOS but the same thing is fragile as shit on Android? Why the fuck there's a thousand of different versions of every Android package and every single one breaks another? Why the fuck Android is so fragmented... If this piece of shit is the definition of "openness" then I'd really prefer the "closeness" of iOS... Totally reminds me of how much I hated IE6 back in the web development days

*Turns on computer*

Hmmm, must be getting that time to do a full format... Wait, my HDD is being a bit weird...

*Runs disk optimise*

- No problems detected, disk %67 fragmented

Ah huh... That would explain a lot, but how the fuck did this happen so quickly 0.o

It is fucking written in rules that SLA would be given post the discussion.

AFTER THE MOTHERFUCKING DISCUSSION.

Bitch can't read a simple English statement.

And in the SLA column, it is clearly mentioned that one must state the DATE. This idiot mentions the entire fucking Quarter.

How fucking dumb you can be to not read the basics mentioned for your own and others ease of functioning.

Indians are illiterate morons. I apologise to the entire world today on behalf of these fragmented cauliflowers.

To whoever this means, I am sorry that you have to deal with these retarded brains.

Also, the task was supposed to be done by others and not the blabbering bitch. She takes up random unwated shit and then cribs to our manager that she is overloaded and Floyd isn't helping.

When I help, she complains that I am overstepping.

Go fuck yourself you mongoose.

Thought the day would never come but... I'm starting to hate android as an operating system...

It's just becoming so inconsistent and fragmented, it's almost at windows level of inconsistent.

Now either google should start regulating the app store and android itself or completely ditch android as a complete stand alone OS.

I would personally seperate android into a runtime and focus on fuschia by building the android runtime into it, that way it could pull system UI element design and such rather than have the user build apps that look completely out of place and don't follow rules like dark mode, theming and the such...

I'm not going to jump ship into iOS because fuck iOS but just really hope google really starting tightening android up else I feel like it's just going to starting breaking more and more into a steaming mess.

Title: "Wizard of Alzheimer's: Memories of Magic"

Setting:
You play as an elderly wizard who has been diagnosed with Alzheimer's disease. As your memories fade, so does your grasp on the magical world you once knew. You must navigate the fragmented and ever-changing landscapes of your own mind, casting spells and piecing together the remnants of your magical knowledge to delay the progression of the disease and preserve your most precious memories.

Gameplay:
1. Procedurally generated memories: Each playthrough generates a unique labyrinth of memories, representing different aspects and moments of your life as a wizard.

2. Memory loss mechanic: As you progress through the game, your memories will gradually fade, affecting your abilities, available spells, and the layout of the world around you.

3. Spell crafting: Collect fragments of your magical knowledge and combine them to craft powerful spells. However, as your memory deteriorates, you'll need to adapt your spellcasting to your changing abilities.

4. Mnemonic puzzles: Solve puzzles and challenges that require you to recall specific memories or piece together fragments of your past to progress.

5. Emotional companions: Encounter manifestations of your emotions, such as Joy, Fear, or Regret. Interact with them to gain insight into your past and unlock new abilities or paths forward.

6. Boss battles against Alzheimer's: Face off against physical manifestations of Alzheimer's disease, representing the different stages of cognitive decline. Use your spells and wits to overcome these challenges and momentarily push back the progression of the disease.

7. Memory anchors: Discover and collect significant objects or mementos from your past that serve as memory anchors. These anchors help you maintain a grasp on reality and slow down the rate of memory loss.

8. Branching skill trees: Develop your wizard's abilities across multiple skill trees, focusing on different schools of magic or mental faculties, such as Concentration, Reasoning, or Creativity.

9. Lucid moments: Experience brief periods of clarity where your memories and abilities are temporarily restored. Make the most of these moments to progress further or uncover crucial secrets.

10. Bittersweet ending: As you delve deeper into your own mind, you'll confront the inevitability of your condition while celebrating the rich magical life you've lived. The game's ending will be a poignant reflection on the power of memories and the legacy you leave behind.

In "Wizard of Alzheimer's: Memories of Magic," you'll embark on a deeply personal journey through the fragmented landscapes of a once-powerful mind. As you navigate the challenges posed by Alzheimer's disease, you'll rediscover the magic you once wielded, cherish the memories you hold dear, and leave a lasting impact on the magical world you've called home.

LMAO

TL;DR Calendar services sucks.

Imagine yourself as startup. You don't want to spend fortune on paying $5 per user per month for Google Services. Also you don't want to pay that to Microsoft for O365. You want to run it itself because you already have droplet running with your other services (ERP for example. Funny story too btw.) Ok, decision has been made, let install something.

I have pretty good experience with OwnCloud from past as Cloud file sharing service. Calendar is not bad for single user purpose (understand it as personal calendar, no invitations to others, sharing is maximum I tried) What can possibly go wrong when I deploy that and use its Calendar?

Well, lot. OwnCloud itself runs well (no rant here) but Calendar is such pain in ass. Trouble is with CalDav under hood and its fragmented standards. So, you want to send invitation to your team for recurrent meeting. Nothing weird. It sends as one invitation to each one, good. Now you realize you have a conflict, so you need to change time of one occurence. Move it, send update. And here comes shitstorm. It is not able to bisect one occurence from series. So it splits it to separate events and send invitation for every single one. 30 INVITATIONS IN 2 SECONDS! Holy sh*t! You want to revert that. Nope, won't do. So you accept your destiny and manually erase every single one with memo in head about planning recurring events.

Another funny issue is when SwiftMailer library (which is responsive for sending e-mails from OwnCloud) goes to spamming mayhem. It is pretty easy to do. When e-mail doesn't comply to RFC, it is rejected, right? So if because of some error CalDav client passes non-compliant e-mail (space as last character is non-compliant btw) and SwiftMailer tries to send it to multiple recepients (one of them is broken, rest is fine), it results in repetitive sending same invitation over and over in 30 minute interval. Sweet.

So now I am sitting in front of browser, looking for alternatives. Not much to choose from. I guess I'll try SOGO. It looks nice. For now.

Learning Java Spring, their official documentation is a fucking mess. Can't get any useful information other than got dumped with loads of confusing terms/packages references/libraries.

baeldung blog site is better than the docs to some extend, but still, very fragmented information.

Ok enough ranting.. Any good learning resource recommendation? Forum?

Holy fuck AMD really have made a comeback... NVIDIA is admitting they lost (how I interpret this, no flame) and then we have Intel literally running their already fragmented CPU range into a ditch of mismatched specs and just brute forcing higher cord counts on an almost out of date manufacturing process...

And now AMD is also releasing new mobile chipsets with integrated Vega graphics (on the zen based chips) that are already outperforming the closest Intel competitor on thermal and raw performance...

What the fuck!!!

AMD might actually become Intel and NVIDIA rolled into one the way they are going in my eyes...

A long struggle to change a nazi enforced scrum methodology that cut our efficency, technical standard and dedication to the product by just working on fragmented features that were added and removed by the wim of the PM.

Job offer in hand as senior dev somewhere else, I stayed, got better eventually. My old boss kept complaining on me for years in performance reviews that I did not respect managements decisions.

Two years of badly led scrum regime left our product in a spagetti mess that is still trying to be untangled.
Til this day, if I hear someone mutter "scrum", I feel a strong need to run far far away.

Linux is great - to tinker, to pull in all your FOSS, mess around...
But it's so fucked up, if you actually build and maintain a product on it, i.e. try to distribute s.th. in binary for money even. It's just not intended. If you offer your code for free, you can always say: "Ah, just compile it yourself. You might need these 29 dependencies, of which 2 are not even checked by configure, oops, and now it crashes, maybe in that qt library version, you picked there's still a bug?.. you know, it worked on my machine, sorry."
But if you sell it, it better install and run! And even if you target only the main distros of all that fragmented Linuverse - let's say, Debian, Ubuntu, RHEL, CentOS, Fedora, and if you're in Germany OpenSuSE and SLES, you'll start to see the crap of work you're up with. What you could try is to orchestrate a docker fleet with one container per distro, where you take the oldest version you still support compile a newer gcc there (to at least have C++11) and all your third party libs and then hope the resulting binary runs on all the newer versions of that distro, too.
(You could even be so brave as to try to pick a deb and rpm distro to build for all other distros.)
But ABI incompatibility can still bite you. For instance we once had the insane case, that our GUI would no longer start just by switching the Window-Manager to KDE.

I'm so tired of all these new support channels. Why the fuck would I want 7 electron based apps/accounts just to ask questions or provide support? I don't want slack, gitter, discord, zulip and what not. Can't keep up with this bullshit.

Can we please get back to supporting open source on IRC? And fuck my life even that got split up due to shit happening in freenode (the company). FML distributed good, fragmented bad.

One of these days i'm gonna pop a blood vessel, trying to keep all my dotfiles organized: syncing the files themselves is easy, just shove them into git, the problem is that i have to install dependencies on different distros (Arch, Debian and Ubuntu):

The package names are different, the paths are different, fuck with Debian i need to compile from source anyway because most of the packages i need aren't available. Its taking me so much time writing distro-specific installers, just so i can deploy my setup on different machines...

Its at times like these that you appreciate just how mind-boggling fragmented Linux is as a platform :D

so apparently my desktop hdd is going bad in the most infuriating way possible: Read speeds are perfectly fine, but write speeds are literally peaking at 600 BYTES PER SECOND. I waited A LITERAL 25 MINUTES (i timed it, 24m51s) to get to the login process. It's performing worse than 320k floppies do.

The disk is 13% full and 0% fragmented. It's negotiating SATA 3.

Time to w&r ig

Ah... Android layout frustrations... Now I can laugh about it and enjoy my #rant-commit from yesterday.

But seriously, I can't wait for Android to be over in 2017... The framework grew into a massive pile of fragmented, fermented and undocumented shit, that gets smellier every Google I/O when they try to flush it down the toilet, but it gets stuck.

This has nothing to do wiv developing stuff this site was created for. I just wanted to make a short public statement and there really isn't any place else to say it without the idea that some oik would infantalize it and make fun.
It goes under the heading of something like, "Personal Irony: I'm Not Codependent, I'm Just Trying to Help [Myself]!"
In 2016 I created a playlist that included REM's "Let Me In," Michael Stipe's song to Kurt Cobain. And "Head Down", and "Black Hole Sun," by Soundgarden. I have a good singing voice, I think it's a baritone. But those notes at the end of BHS, you know, "Won't you come?" When you sing it, you pronounce the lyric: WOAN CHOO CU-UH-UHM, the "UH-" dropping an octave into "UHM." It's particular to my range that dropping that note requires discipline and concentration. And even then I'd say I've sung it 100 times and nailed it to my satisfaction maybe twice. Anyway, I had these two songs as a playlist in my media player. I listened to them and sang along as quietly as I could, it being four a.m. here in Seattle. And as the final notes of BHS fragmented and skipped back into eternity, I felt like total shit. Not at all normal for me to personally feel the loss of an entertainer, but at that moment I did feel sad. That's it. Thanks for reading this odd little collection of words.

I simplified 7 functions down to a blob because it was truly unreadable and fragmented. As I did it, I thought there was no way I did it right. This can't be the logic. Nope. It is.

Yeah, the formatting could be better. End of the shift so that's a tomorrow thing.

Shitty goddamn "Agencies" and the piece of shit WordPress install garbage that comes along with them

150+ fucking plugins
Cause this is 2018 and more plugins = better wordpress site right?

CSS is easy enough > just edit the stylesheet right? I mean theres already CSS in there so this should work.

Fucking Noooope because the default custom style sheet doesn't get loaded through the garbage theme anymore.

Sure that makes alot of fucking sense sense, idiots added another fucking plugin for Custom CSS ontop of the "Live CSS Editor" ontop of the "Click and Place Builder"

WHAT IN THE FUCK

Can someone explain to me why these "Agencies" need to add 50 plugins just to edit fucking visuals? And when they decide they don't want to use that plugin anymore > add a new one, but we won't keep everything clean and in one place > lets just fucking leave it installed and fragmented for the next poor fucker that comes alone