Doches

> It turns out we don’t have to care about any of this [...], so none of this matters in any kind of deep way, but: we’ve decided to just be a blog again, so: we had to learn this, and now you do too.

I found this closing sentence utterly delightful, particularly in an age of endlessly filtering every piece of text I read on the internet through a mental "was this written by Claude, Codex, or (just possibly) a human?" filter.

Skywise is basically a re-branded Palantir Foundry, and Palantir’s not exactly a big believer in avoiding US tech…

Did you look at them, or did you just tell Claude to look at them? /s

Seriously, though — if the history is valuable and interesting, include it. If it provides context in general, include it; if it’s just overconfident marketing fluff straight from the parrot’s mouth, drop it. I like my READMEs to open with the ‘why’ of the project: why I built it and why you might need it too.

Truly evidence that we’re living in the worst timeline — the Bulwer-Lytton has been one of the highlights of my year for as long as I can remember. My parents introduced me to it before I could read; I remember them laughing and crying as they tried to explain to four-year-old me why this one inscrutable sentence was the funniest thing on earth. I’ve looked forward to it ever since, though recently I’ve only checked in to read the dishonorable mentions and winners once every few years.

Knowing I’ll never again check and find a year’s crop of perfect sentences dims the light more than I would have expected. Sad times.

> Endpoint views break down request volume, errors, latency, and status codes. Crash and ANR detail adds the app version, device, and thread context around a failure. This is where a problematic UI transition can be connected to a backend or runtime condition.

The project README reads like a first draft straight out of Claude, and it's incredibly off-putting. The 'Show HN' post here is so much better; clearly you're capable of writing a decent explanation of what this project is, its history, and for whom you've built it. Take the time and write the damn README yourself.

If you expect human attention, put in human effort.

You're a sophomore at UT, so as a UTCS alum (:wave: from a fellow Turing Scholar) I'm not letting you off the hook. Unless things have majorly changed, I know you're taking 6 hours of writing-heavy coursework.

That's up to GoG; I've submitted every game I've released to them and it's like talking into the void, never a response. They're a delight as a customer, but kind of half-assed as a platform (at least if you're a self-published indie).

Ooh! I’d love to see that, or to have a chat and swap ideas. My email is in my profile if you’d be up for it.

You’ve got me; I was very much a Battle Chess addict once upon a time…

I know this is nitpicking, but as a Texan I have to correct you on a point of grammar. The “west” in “West Texas” (and similarly for the other regions) isn’t an adjective; it’s part of the proper noun and should be capitalized. So it’s “West Texas,” not “west Texas.”

Yes, this is weird and no, I have no idea why we do it, but it’s really weird to read “export it to east Texas” — to the extent that I had to re-parse the sentence to figure out what you meant.