My God. He may have died, but can any of us truly say we have lived half as much as he did?

Yeah but that’s a whole next day away.

I finally found the answer to all problems in my life: just be motivated to do things. I’ll start tomorrow…well, next week at the latest.

I did not plan for this, in hindsight, inevitable eventuality

Man, demons have the best parties.

The secret to all issues in code and in life.

I wouldn’t deploy this for my fucking dog, roll it back now!

It’s got what shareholders crave

I enjoyed the joke but yeah I thought Rust was known for quite good error messages in general. I haven’t used it though myself.

Not…for a jedi

This isn’t a car

So…your face or mine?

I don’t think that will work, but hopefully they raise income taxes so I at least take home a bit more cash each month.

This is my headcanon when I see a simple but long lasting bug like this at a large company.

To you or I, it seems simple. Clearly things are not working as intended and the fix is trivial. Raise a bug in the tracking system if you really have to, then just fix it, right?

Here’s the thing. That code was written completely according to the specification. The path there was clearly there in the requirements. So what? So…that means it’s not a bug, it’s a feature change. And if it’s not a bug, that means we can’t officially use our allocated (but always shrinking) bugfix time to work on it.

If we want to fix it, we need to put in a feature change request. That means we have to articulate the value to the business in changing this feature and explain why we think the original specification is wrong. We can’t get confirmation from the spec author because they are no longer with the company. That means we have to prove that it was written incorrectly.

If…and that’s a big if, we can articulate that there’s business value in doing this and that the original specification was likely incorrect, then we get to the really fun part. Prioritisation.

You see, the team that built that feature doesn’t exist anymore. Once the bulk of the features were done, they got disbanded and the engineers moved to other teams. Technically there should be a single team responsible for every feature so it gets maintained, but in practice it doesn’t really work that way. The people on the official team that’s responsible haven’t touched any of that code. They’re not too keen on starting either because they have their own priorities.

So after all that, the task sits in the backlog of that team, neglected. Eventually in some distanct sprint planning session it will be flagged as an old ticket. You, who raised it, would have left the company and nobody in the meeting has context about why the task was created. Isn’t that miscategorised, shouldn’t it be a bug? Why is it with our team, is it even worth doing? Then it will be pruned from the backlog. The sad task that was fought for so valiantly, only to die sadly in the cutting room floor of a backlog grooming session.

Then one day, the bug will annoy a newcomer so much, they’ll just sneak the change in under another ticket and the bug will finally be fixed. Months before the product gets scrapped for a worse replacement. What are the specifications of the replacement software based on? That’s right, the original specs of the old system to ensure backwards compatibility.

Well, we each have our talents.

Make sure to hold on tight with both cheeks

The enemy is both strong and weak

Then by shooting your refrigerator you turn it into a hot war… ironic

Why does nobody think of the boulder?

I personally drive my car like a maniac therefore this study must be false… really?