After a software incident, remember to use the 3,125 whys methodology to find issues

We should use X, it's "industry standard" ... But what if I can't say I'm impressed with what this industry achieves as a "standard"?

Underrated opinion!

LLMs will never get meaningfully better than they are now

dax It'll be a long time before we fully take advantage of how good they are already

Looks like my best work contribution today will be asking: "are we sure that's actually a problem?"

Cursor's biggest lie: "Ah, now I understand the issue!"

Today's AI gem: being announced in May 2025 (which is in the future), so it's likely a hypothetical format for this project.

I unironically miss working with Angular 1 ¯\_(ツ)_/¯

Every time I read "focus on outcomes over output" it sounds like "yeah, don't waste time training for the olympics... just win them"

acoustic coding 🤣

AI generated background images make online meetings so much more fun

Fedora. I think ...

Dude, if PHP folks can be passionate, then that's not a valid reason not to be passionate about .NET!

My "favorite" is "It's not made for that". Who cares? If ti works great at doing "that" for our specific use case! Remember, bubble wrap was meant to be wall decor, not to wrap packages. Where do we go with "not made for that"?

Here. Here is a worse place.

2 things can be true at once is not what the internet understands the best!

COBOL!

Water's pretty dope. Tea too.