(Yes, I finally saw it, and it was very pretty and I have thoughts)

amaze amaze amaze

As a gamedev, wearing jeans to work is not unprofessional, using informal language with a customer is not unprofessional, but I *would* say that calling your coworker's code "trash" and writing commit descriptions that just say "fixed shit" is unprofessional

Yeah, all of this. I would have said that "professional" means taking your job seriously and showing respect for your coworkers and customers, and has little to do with the specifics of your presentation (except insofar as they enable the former)

But also, I think there's a big fraction of the industry that *never* cared about these things and only ever pretended to; saying the "right" things and being visibly Orthodox in public to put themselves on the radar for promotion and hiring. Never about the code, always about the money and respect

Maybe they think AI replaces *reading* code as well as writing it. A lot of things we think of as "good code" would no longer matter to such people because those things only existed in the first place to reduce the friction of code reading, debugging, and maintenance by humans

I don't want to see more than 100 lines of code changed in a single commit if possible. Exceptions made for refactoring fixup that HAS to be done all in one go (eg. I change a variable name that's used in 200 places)

This is yet another reason to prefer making small, atomic changes. The approach some programmers have of "commit everything in my workspace when I get a thing working" rather than putting in the effort to decompose things leads to so many issues getting missed and makes them harder to fix later.

It's RIGHT THERE. You can download for free.

I just don't understand.

I don't understand why there are so many genAI "photos" of Artemis II going around when the actual imagery is easily available and gorgeous.

Like, look at this stuff www.nasa.gov/gallery/arte...

Is that AI-generated? I was watching the livestream and in the imagery I saw, the parachute lines were much longer at splashdown and the capsule was not in the least bit shiny after its descent through the atmosphere.

This is an actual, official photo for comparison: www.nasa.gov/image-detail...

I'm moonscrolling

Part of "code quality" is also "can this be understood by an average-context human being reading it." Can we really trust a LLM to simulate how humans read things?

We don't need to speed up production. We need to slow down.

We don't need to write code faster. We need to think through what we write.

We've spent decades working to ship faster, and that's landed us in a world of hurt.

Build better products, not faster.

Weren't Gemini 6A and Gemini 7 technically "separate missions?" Same goes for Vostok 3 and 4; Wiki even explicitly calls their communications "the first ship-to-ship communications in space."

scene from lord of the rings "this is it, if I take one more step it'll be the farthest away from home I've ever been"

Artemis II today.

If I were an indie, I think I would still keep a devlog, but that would be for rubberducking and documentation purposes and I don't think I'd publish it publicly. I've found that the rubberducking benefits alone of journaling as I'm working outweigh what time is lost typing my thoughts up

I had a pleasant dream where I woke up in my bed as usual, but there was a cat

I was forever converted to Oxford comma usage by this comic years and years ago.

I know the tweet is Al generated when they use " ," before and.

“I will NOT sacrifice the Oxford comma. We've made too many compromises already; too many retreats. They assimilate the em dash and we fall back. They capture ‘not just X but y’ and we fall back. Not again. The line must be drawn here! This far, no further!”

What does your test harness code look like for this? I've worked with these kinds of tests in the past, but the biggest problem I've always had with them is that they were a lot flakier and complicated to author than unit tests, which mostly had to do with how the harness was implemented

This is so, so well-articulated.

SPACESHIP

Getting to hear Victor Glover's stream of consciousness while he's testing how the RCS handles on manual makes up for a bunch of it. I miss the shuttle-era tank-mounted rocketcams, though

Game workers do not receive any residuals/royalties on shipped titles and shipping bonuses are increasingly rare. There's also no guarantee that your name will even be in the credits if you leave before ship, and studios will use this to keep you compliant.

All of this can and should change.

The world of Hail Mary: the world is faced with an existential threat, works together, and puts trust in scientists to fix it.

Our world: science grants stripped for blatantly hateful/stupid reasons, our health secretary is against vaccines, and our president hates wind power.

Clearly no politics

Why do you need so much boilerplate and repetitive code in the first place?

More and more I feel like I'm the only programmer I know who still actually likes *programming*

Where was the part where you started to struggle with the text, out of curiosity?

Blue Prince: Psych, this isn't the real ending, here's another door you need to unlock!