Pinned Tweet
Alright, y’all. The time has come.
Most of my friends and colleagues have left. The algorithm is angertainment. And the new owner turned into another Rupert Murdoch.
I think I’m done here.
Karl Isenberg, signing off.
I did not expect the skill tree in #DragonAgeVeilguard to be so much like Path of Exile’s.
Metrics are customer facing APIs.
Don’t go adding metrics willy-nilly just because you think they might be useful.
You are going to need to maintain those suckers forever to avoid breaking customer metric queries and alerts.
Ever get half way through a refactor and just give up because the code is just a giant ball of tangled spaghetti?
Oh hey, GitHub Copilot now works with Gemini, and it's 2 million token context. I wonder if the experience is better on Go projects with lots of vendored dependencies.
cloud.google.com/blog/produc…
Looks like you can alternatively choose Claude, o1, and the original Codex GPT-3.
github.blog/news-insights/pr…
He did!
As alternate Boimler gets up to take command of the USS Cerritos at the end of #StarTrekLowerDecks' "Dos Cerritos", he performs the Riker maneuver on the bridge! -)
Karl retweeted
Hey @X can I just get a “no politics” button? I’m only on this platform for tech info. Fighting your algorithm sucks.
If changing your API is slow, expensive, and disruptive, you can’t just deliver MVPs and fix them later. You need to consider all the possible ways the requirements might change in the future and make the API flexible enough to avoid needing to make breaking changes.