How often do you ask questions the answers to which you don’t truly care about?

Tests are failing successfully. Tests are working correctly. Maybe tests are failing but for incorrect reasons. Test checkers are failing as well but are they failing correctly? The checker testers are failing too. Checking the test checker tester tests.

Some Logs:

log_1.txt
log_2.txt
log1.txt
log2.txt
log3.txt
…
…
log8.txt
log9.txt

log_one.txt
log_two.txt
log_works.txt
log_pass.txt
log_fail.txt
log_pass2.txt
log_fail2.txt

My shoes have started to quack like a duck.
(Only when I walk. It would worry me if they quacked otherwise. The quack occurs with every step upon the shoe landing on the ground with the natural force of walking.)

Anyway, I walk really fast and people have started to give me way because they probably think it’s a kid on a rampage. Which… works for me. So yay.

How far do you run from it? And how much do you turn from horizontal? Can you see it then?

People exist, who split up their work into 1176470588235294 tiny little patches all with related changes to showcase productivity.

Just visiting a friend. Ringing the doorbell.

Today I am proud,
because I kept going.

I didn’t give up,
because I needed to reach it.

My finger moved fast,
tapped so fast and I felt it closing in.

So close… oh so close.

It was getting hot.
My vision started to blur,
and yet I could not stop.

I hit the key one more time,
and found my bloody command.

Today, I got startled by my own reflection.

gut add spaghetti.cpp

A && B && !C ? x : A && C ? y : x

I said “Thank You, Machine” after it scanned my ticket and let me through.

I find this mildly amusing.

So when code is badly written, more corner cases are unnecessarily introduced. And it’s sometimes tricky to find the corner cases and probably messy to fix the corner cases.
And so the code grows in size as a result. And when these fixes to the corner cases are not well done, they introduce more corner cases.
So what results is a large collection of corner cases. Only corner cases remain when this goes on for a while.
Because of this, every new feature can be effectively translated to a collection of corner cases to be implemented.
As corners grow, triangles become circles and tetrahedrons become spheres.

I live in such a sphere.

Let a clean uninstall script be a thing for all packages if you build from source and install.

Anyone uses rtags for C++ code browsing?
It’s pretty accurate since it’s based on clang but it’s a bit slow sometimes.

It appears to be using a weird amount of memory though.

Where am I going?

You used to think that it was so easy.
You used to say that it was so easy.
But you’re tryin’, you’re tryin’ now.

More fzf: deeper integration with other dev tools I use.

"A or B ?"
"Yes. A or B."

Why do I bother.

auto abuse = veryReabab1eShet();
auto moreAbuse = n0tRealyNo();
auto ohNo = abuse(moreAbuse);

Why are the clouds all lined up ?

I'm obsessed with convex hulls.

Fuck all of this. I wanna move to The Shire.

Right. Should've known to install Pkg first.

My luck.🤦‍♂️ Lost a perfectly good kite of my own making. Goodbye friend.

If your “solution” fixes the test case which is failing, it does NOT guarantee that it is the correct fix. You don’t just blindly change whatever piece of code you like to make just the test case pass. You actually also need to analyse the code and ensure that the rest of the intended functionality is still intact.

Nice menu.
I’d like a No tech support sandwich please.

I can’t even wait for my copy of Leviathan Falls to arrive. I’m so tempted to read the All Spoilers thread on Reddit. Aaaaaaaaaaaaa! C’mon... you can do this. Just a couple more days.

Let me make this clear.. overusing ξ, ζ and ς in your equations or formulae does not(!!) make you smart!