As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

I don't understand why people tend to shit on certain languages.
I`ve seen my fair share of shit software written in a plethora of languages, and the problem was usually that the devs used the language/framework completely wrong.
Languages and frameworks are designed to solve problems, if you don`t use them in the correct way then you are to blame.

It is like sticking your dick in the exhaust pipe of a Volvo, and then writing a Medium post complaining about your charred dick and how all Volvo's suck. Yeah I'm talking about you PHP haters, all of you that shit on Java on a daily basis and you morons saying "python is slow"

Don't get me wrong, I send PHP shitposts/memes all day to my friends working with it. But if my code doesn't work, it is my fault and I own up to it.

With that said, I will blow my brains out before writing a single line more of PHP

Rant over

I'm curious, is email campaigns such as 'constant contact' part of a devs job? new job wants me to be in charge of this and I could not think of a worse job I would like to do.

I don't even check my own email!
I hate social media and suck at posting anything besides random useless memes.

REALLY??! Email campaign????

Everywhere you go, you find these memes where developers are skeptical of their work. Things like "It works. I don't know how. It doesn't work. I don't know how.". Don't you guys think this is a huge problem? And people say that their programming language is the best, because preference. But isn't this happening because our tools suck?

Yes the problems maybe inherently complex but at least we should be able to figure out the logic behind the snipper and reason about it.

Haven't really experienced it, but they say Haskell and the likes are great at this and it must be true because it's backed by mathematical properties and laws, not " experience".

So the rant here is, wish we had better tools in the mainstream that allowed us to enjoy absolute faith in at least what we have written, regardless of the fact that we understood the problem in the domain.

Feature request: if everyone tagged memes and funnies with, say, meme, that way we could have a special feed for those. Some like em, some dislike em, everybody wins!
If a rant is really a meme, and it is not tagged as such, the downvote menu could include a "It's a meme" selection which would promote it to that feed. Whadda y'all say?