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.

My "Coding Standards" for my dev team

1.) Every developer thinks or have thought their shit don't stink. If you think you have the best code, submit it to your peers for review. The results may surprise you.

2.) It doesn't matter if you've been working here for a day or ten years. Everyone's input is valuable. I don't care if you're the best damn programmer. If you ever pull rank or seniority on someone who is trying to help, even if it isn't necessarily valid or helpful, please have your resume ready to work elsewhere.

3.) Every language is great and every language sucks in their own ways. We don't have time for a measuring contest. The only time a language debate should arise is for the goal of finding the right one for the project at hand.

4.) Comment your code. We don't have time to investigate what the structure and purpose of your code is when we need to extend upon it.

5.) If you use someone else's work, give them the credit in your comments. Plagiarism will not be tolerated.

6.) If you use flash, you will be taken out back and shot. If you survive, you will be shot again.

7.) If you load jQuery for the sole purpose of writing a simple function, #6 applies.

8.) Unless it is an actual picture, there is little to no reason for not utilizing CSS. That's what it's there for.

9.) We don't support any version of Internet Explorer and Edge other than the latest versions, and only layout/alignment fixes will be bothered with.

10.) If you are struggling with a task, reach out. While you should be able to work independently, it doesn't make sense to waste your time and everyone else's to not seek assistance when needed.

11.) I'm serious about #6 and #7. Don't do it.

CS Professor: “What M word is the black hole to all productivity?”

Student: “Management”

CS Professor: “Was going to say meetings but that’s better”

After my college I was about to start freelancing.
I met a client and had a chat with him about requirements and all.
He was really nice guy. Then he asked me "What will be the size of the website?? A4 or Bigger??.
On the next day I started looking for full time jobs.

Poetry at work!
Thats a good usage of a whiteboard 😁

JavaScript is wild

Can you log out of Facebook and LinkedIn? Cool. That'll be £50 please.

I don't know how to interpret this ..

I was registering for a website, and on a whim, I used this as my username:
null'); PRINT('Hello');--

And sure enough, the login system went down. The next day it was still down, so I went to Twitter to tell the people running the site that this was why, but to my surprise, I see them saying they had been hacked.
Based on the timing, I'm pretty sure they're referring to this, but they are saying user info was stolen. *facepalm*
They later said they stored passwords salted with a fixed salt and hashed with fucking md5, at which point I was glad not to have done any more business with them.

How incompetent can these fucking people be?!

As a Python user and the fucking unicode mess, this is sooooo mean!

True evil

Programmers are like cats, you need at least two of them so they can play with eachother

When your boss asks you to debug some crappy legacy code and you need to bring in the heavy artillery

I am so sick and tired of hearing "I'm not good with computers" from these god damn secretaries I have to work with.

Fuck you! I mean, seriously, FUCK YOU! That God damn piece of shit Windows XP door stop has been on your desk for at LEAST a decade (shit, I think that was the same PC my highschool had, and I'm in my mid thirties)!

What in the FUCK do you mean you don't know the difference between files and folder? How? HOW can you stare at that damn screen every fucking work day off your life and not grasp simple concepts!

And FUCK THE ADMINISTRATION for hiring these volunteerily ignorant babies who refuse to bother figuring out more than just where the power button is (and, fuck me, even THAT took years).

Fuck me if, after spending 40 God damn minutes of my time trying to guide some secretary, who's been working twice as long as I have and making probably twice as much, on how to copy a file from one folder to another, I have to listen to some fucking pity speech "I just don't get this high tech computer stuff. I'm just too old"

And FUCK society for allowing this fucking behavior! I don't know any other piece of technology where people are happy being so blindly ignorant to even the basics! I don't know Jack shit about the internal working of a car, but I know where and how to use my steering wheel and peddles and that I need to take the thing for an oil change. Hell, I even know when my tires look bad... If I can do that, you can fucking learn how to copy a god damn file without needing me to help you... FOR A FUCKING HOUR!

FUUUUCK!

*Takes a deep breath*
So... How was your day?

Let's make a story, 3 words each. I'll start:

A month ago,

How?
Is it a test?

Client: "Why is this taking so long. I could do this."
Me:

Yes, this is actually a real thing.

I wonder in what you learn in the prerequisite "Keyboard and Mouse skills" class if this one teaches you how to type and delete text...

!rant
Reddit comment on a thread about Joomla! sites being vulnerable to SQL-injections:

"Joomla sites are so infested they became sentient.

Joomla sites needs no webmaster, some one else will administer it for you.

Joomla sites have very good SEO, specially in "v1agra c1alis p3nis size"

Traffic count with Joomla is high, all the bots breaking all the vulnerabilities count for somethin'."

😂 Pure gold.

Exception handling.

This is what our university recommends as reading material for databases. I'm still in denial that this exists.

I think I just invented a thing.

Mouse drop.

It should be a thing.

The next time I switch jobs I'll definitely do a mouse drop before I leave the building.