Fixed obvious bugs.

Tests started to fail.

All error messages read similarly—“Feature XXX contains an obvious bug blah blah blah. It’s supposed to fail, but it’s not.”

F____!!!!!

Changed colour scheme from Monokai to Spacegray Base 16 eighties. Instant euphoria!

I'm a bit cornered. A week into an ambitious refactoring effort that was supposed to take just a couple of days to finish, the end doesn't seem anywhere near. The system went from a messy albeit perfectly functional state to a much better structured non functional bag of bugs. If I leave the branch all the efforts are lost. If I soldier forward I'll be unproductive for good knows how many days to come.

How did I ever fuck myself so hard!

Wondering around some code and I found:

// The next few lines of code should be fairly self-explanatory
// ...

Well if it were so self-explanatory then why TF putting up a comment here!!

Git blame file

Oh sugar it was written by me...

One more small feature

What a lie

I was trying to get some cash from an ATM. Instead of vending bank notes as it should, this happened...

I still need that cash...

4861707079203230313721

DeathStar 3.0

The railway service in Sydney is called CityRail.

Fuck CityRail!

It's so unreliable that service disruption is to be expected when the weather is too hot, too cold, too wet, or too dry. If it rains, some services will be cancelled while the rest face delays.

Fuck CityRail!

The rail network is so dilapidated it costs the government millions of dollars each year for maintenance, despite charging a fare that is one of the most expensive.

Fuck CityRail!

Now I'm typing this because I've be stuck on this train for the last hour and there little hope for me to reach home before fucking MIDNIGHT!

FUCK CITYRAIL!

They initially offered replacement service but later retracted.

Fuck CityRail!

Time flies when deadlines are close.

Why does GDB always set the bloody break point one line above or below where I want it to be. This is driving me nuts. It's like its author deliberately planted a nasty practical joke in the code.

This is actually an advice given to me:

"Only ever release your code on a Friday, preferably after 6pm. If you're not confident enough to do that, your code is not ready."

Who says dev doesn't require courage.

"Measure once, cut twice."

Base64 "encryption"

RSI. Seriously I thought I am immune for the last two decades and now it's catching up on me. One of these days I'm gonna really learn VIM just to cut down on mouse usage.

Open inspector from Chrome in front of your friends and proceed to deleting annoying ads or bypassing scripts like a boss.

What's the worst bug? Schrödinger's bug, one that only appears when the debugger is not attached, and your test instruments are disabled.

I'm looking for the maximum -- one can attain from a single post. Please down vote this if you will.

print(). Nothing ever gets done without it. Not even hello world.

Just upgraded my heavy duty debugger. What do you folks think?

Was in a university group project and had to make an angular momentum measurement device. An hour before demo voltage on one of the pins was still a bit too high. Friend drove to Chinatown not too far away from campus and bought a pack of the cheapest batteries. Plugged the cheap batteries in, the voltage was just spot on. How awesome was that!

$gcc -O3 plan.c -o mylife
$gdb mylife

As a dev living overseas I video chat with my family every Wednesday after dinner--a ritual to keep the family bond strong.

A ritual I dread.

While my cousin who works in hospitality always brings up interesting stories from her work, I have little to say about mine.

Sometimes my mom complains me being secretive of what I do. Everytime she says it I cry a little inside.

Remember those innocent looking two lines of code that you didn't write a test case for, because they can't possible break, right? Well, they are going to fuck you up.

Spent 2 days carefully crafting a highly optimised routine, then spent 3 minutes to write an unoptimised version for benchmarking. The latter ran 50% faster.

I used to have this awesome co-worker who patiently listens to me ranting everything all day long. Well that's before devrant came along.

When the source code of a library that you depend upon is easier to read than its official shitty documentation...

Just spent 3 hours on a segfault bug that could have been prevented had I been diligently putting const where it should be. Shame on me. Never be too lazy for const-correctness ever ever ever...

I was once working on a grand vision of a suite of analytical tools, which later turned into a single web app, which later turned into a desktop app, which eventually turned into a command line app, which ultimately turned into a background service that writes the results of a small subset of what it was supposed to do into database tables.

Thanks DevRant, I've received the sticks and it's now right where it should be 😀