In a professional setting, sometimes the cost of developing something more performant in C is not worth it. The velocity unlocked by creating systems in Go is just incredible, after your company has built everything in C[++] for decades. I find myself creating gRPC APIs in Go to solve most design challenges, because it’s stupid fast to develop and is fairly maintainable after.

Looks more like a Bichon Frise rather than a Poodle - but probably an unnecessary distinction, as it is still cute.

Just started My Little Pony: Tails of Equestria with my wife and 7yo daughter - it’s a blast!

Sometimes I wonder if in 75 years people will look back on our caffeine use in this generation like we currently look back at cocaine use in products in the 19th century. Until then, I continue to slurp down coffee like that is my actual job.

This - no one can agree how long a day, week, month, year etc are!

Like sure it’s 24 hours in a day but is a year 365 days? No, not technically speaking.

Time has always been really hard for programmers.

Can confirm, will destroy the rubber/plastic bits in your toilet.

That being said, I still use them all the time and replace the toilet innerds after a few years. I just would rather clean the toilet every few months and replace toilet parts every few years than clean the toilet all the damn time and have old working toilet parts :shrug:

Well you are not in danger of staying at that hotel now - it’s closed.

And if you were wondering, it was amazing.

Every time we see this in our legacy code we yell out: dolla-dolla bills 'yall!

(after) …ah crap it’s actually selinux…