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.

In electronics there's 3 options.
1. You pay a small fortune to get something decent.
2. You pay a smaller fortune to get crap.
3. You build it yourself and it'll be nicely priced AND decent.

Why is that? I have no idea. Profiteering gluttons perhaps.

Case in point: my watch. A waterproof one, so you'd expect to be able to take it in the shower, which I often did.
But then, le wild drop from 50cm height occurred and the whole thing just popped open, with soapy water rushing in. Luckily it didn't short out, and I quickly evacuated it out of the shower and dipped it with my towel.

Then already I thought.. what the fuck is wrong with the designers of this thing?! I'm all for keeping the inner parts of electronics accessible for self-servicing. But in a waterproof watch you wouldn't expect the backside to pop right off and expose the bloody internals, would you? So that's one thing. While evacuating it I quickly figured that I'd want to remove the battery immediately.. except that fucking thing was screwed in place?! WHAT THE FUCK?!! Use those screws to keep the fucking backside of the watch in place you certified pieces of shit that designed this craptacular piece of garbage!!!

Finished showering, went ahead and troubleshooted the thing. Miraculously it still worked. Except that now the UI of the fucking thing is biting me in the ass. A single button on the watch is used to operate the whole thing, and get it to set itself to the correct time, get radio signal, go in sleep mode (where the watch stops ticking, for storage purposes) and activate itself again. So I dived into the manual.. and still couldn't get it to work properly. So it's got one button just like an iPhone, it craps itself when it's dropped just like an iPhone, its design is shit just like an iPhone, and it's completely unusable when it craps itself just like an iPhone.

And the manual... Oh fucking shit. It specifies that the watch is 3 bar water resistant, yet apparently you can't take it into the shower. 3 FUCKING BAR!!! That's supposed to enable you to take a fucking dive with it! And apparently you can't drop it either.. who would've thought, when they lock it with no more than outwards pressure from the back plate into the main body! How difficult can it be to use fucking screws, and to make it watertight put some rubber bands or whatever?!

CERTIFIED MOTHERFUCKERS!!!

And the watch, it's in the garbage can right now. Right where it belongs!!

does anyone know if theres a way (browser / api / mobile) lying around on devRant to retreive the list of users you have subscribed to?

it looks like someone has a half done project to finish 😢

SSL was a good idea terribly implemented. Relying only on big tech for valid certificates was the single most idiotic thing the web baboons could come up with.

Sure, you could always hack comodo (again) to issue yourself some LAN certs but come on. You either expose your server or pay half a kidney for a somewhat secure thing! Give me a break....