This was brewing in my mind for some time now. Finally put "pen to paper". nlopes.dev/writing/grow...

> I just wanted to express my deepest appreciation for the work you are doing with acdc. At the end of the day this is why I keep doing OSS.

Opus 4.8 on the left, my own on the right.

It still boggles my mind that I can write this at 30000 ft like it's nothing.

I'm adding asciicast support to acdc... which meant creating this today: github.com/nlopes/ascii... I'd rather have this from the asciinema folks but they don't expose the format as a library :(

OMG yes! I didn't realise jj allowed for "private" commits. That's awesome.

99.99% isn't a faster version of 99.95%. It's a different problem entirely. 🔥 Our VP of Engineering @nlopes.dev writes on what autonomous recovery, dependency ceilings, and CI/CD speed actually look like at four nines: incident.io/blog/humans-arent-fast-enough-for-4-nines

With a day out of work to relax, I never thought I'd end learning the spec for the various asciicast version formats. But here we are.

Gosh, having a lot of fun with asciidoc today. I had added a terminal replay feature earlier and now I've been adding asciicast format so if you record something with asciinema you are able to see it being played out in the generated html 👌 Animated gif in the threaded post.

Very much worth a read.

I've added a `[terminal%replay]` block to `acdc`. And then created an `adoc` with the full result of a `cargo nextest`, which now generates this lovely terminal replay in html (using libghostty-vt). github.com/nlopes/acdc/...

Yeah, rust error messages are in a different category altogether.

Michael if it's any consolation, I've just bought Ouros and will be recommending it to everyone. I wish more devs made games like this one, great work!

Google customers: we really need good customer support. Google: here are our new icons. Rejoice.

You're giving too much credit to LLMs. You're not giving enough credit to LLMs. Both can be true. I don't understand what's so complicated about this. And the argument that using LLMs is *only* bad and destructive no longer flies. Even if there's a bubble. Even if said bubble bursts.

Wrote a bunch of words on building acdc: nlopes.dev/writing/buil...

New release of slack-go (pkg.go.dev/github.com/s...) adding support for the Data Table block (docs.slack.dev/reference/bl...).

It's wild that a human can look at jj b m main -t @ and just know what it does. wth

I should say that one of my favourite things about jj is how much faster/better it seems for claude code/codex/etc. I never fear a mess up that is irrecoverable.

Now that jj is in my muscle memory, git is feeling clunkier and clunkier, even though I think I'm pretty good with git plumbing. I still think jj has a way to go to nail the ergonomic for some flows. Not having a staging area, when you get so used to it really messes you up.

Have been speaking with a load of companies adopting AI and there are some clear trends emerging. Written up my thoughts and predictions for those also trying to think ahead! incident.io/blog/eng-in-...

I've added a :terminal-preview: attribute to acdc (github.com/nlopes/acdc/...) that uses libghostty-vt to generate html with the actual terminal with the right ansi colors 👌 #asciidoc #asciidoctor #libghostty

This undercurrent within the #rustlang community (and others) has to stop. The attacks on people simply because they are using developer tools that make them productive is 100% out of line. I can respect the anti-LLM arguments, but let's agree to disagree, respect each other as humans, and move on.

An homage to rust: nlopes.dev/rust-timeline/

JUST ANOTHER DAY OF

There is a great book called Checklist Manifesto which is about how aviation and medicine adopted checklists to improve safety. I’ve found it super useful as an SRE building runbooks, but turns out it applies to AI too. blog.lawrencejones.dev/building-ai-...

Been vibe coding a neat rust release timeline but taking inspiration from newspaper styles. Any folks out there from #rustlang have opinions?

This is such a nerdy movie that I keep re-watching - some parts are really good, others boring. And sometimes the soundtrack is bang on, other times so annoying (the void of space sound that drives me up the walls)

We're now in the script kiddies era of security exploitation using AI.

Oooof mitchellh.com/writing/ghos... Is this the start of something, or at least a sign of things to come? Time will tell but GitHub is not having a great week.

Just got @mara.bsky.social book on rust atomics and locks and I'm quite happy with it. Thank you for writing this up! 🙏

I wonder who is starting now that we'll see as the new Github in a year. Perhaps @ersc.io ? Don't get me wrong, no one is (or should be) quite at a "moving away from Github asap" point but it surely is getting pretty bad.

sub 2h is crazy. Humans never stop impressing me.

With people getting bolder on code changes, both in depth and size, the current state of pull request review is pretty sad. I hope the next year or two bring us much better tooling for this.

Why cargo test when you can cargo nextest? cargo nextest is so ingrained by now that I find myself typing cargo nextest --doc and then realising that's a nope nope nope. 🙈

Ignore the branch name, this is pretty cool. It also allows me to write everything in AsciiDoc now and then if needed convert to the lower fidelity markdown.

I really dislike that @anthropic.com keeps changing the shortcuts in Claude Code. All of a sudden Ctrl-f no longer moves the cursor forward but Ctrl-b still moves the cursor back. Alt-f moves the cursor one word forward though. The input UX seems to go one step forward and two steps back (no pun).

Downplaying Anthropic's claims because you don't like AI is a pretty terrible take. I'd rather take them seriously and then have a bit of a laugh if they overplayed their hand than have a bit of a laugh and then live with terrible outcomes.

I fully agree with this. Same goes for refactors. It's just a lot easier.

This is really really cool: www.reddit.com/r/ClaudeAI/c...

Am speaking at ai.engineer Europe this Friday on "Fighting AI with AI" about how we use AI tooling internally at @incident.io to manage the complexity of building AI SRE. It's at 12:20pm in Fleming on the Coding Agents track for anyone who is around!

This is such a good post x.com/mitchellh/st...

It's still too soon to tell but it seems warranted that Anthropic would do project Glasswing with the information available. Most people overestimate what AI can do in one month and underestimate what it can do in one year.

acdc now generates a nice table with the times taken to parse and convert if given multiple files. It also displays wall clock time 👌

I've started doing some performance work on github.com/nlopes/acdc. I'm quite happy. For small files, acdc (rust) is still slightly worse than asciidoctor (ruby). I need to tackle that. For big files (250Mb), acdc is 23x faster for parsing, and 1.8x faster for conversion. 🤯 #asciidoc #rustlang

Gosh, this behaviour by /r/rust is nonsensical. These occurrences are part of the reason why I wrote nlopes.dev/writing/vibe.... I hope some of this sentiment goes away in time but it sure is exhausting right now.

"We all write shit code sometimes, except now it’s always labelled as AI slop. Sometimes it’s just shit code." I said what I said.

I've written about this: nlopes.dev/writing/vibe...

I did a think again with WASM using Claude Code. In order to commemorate Artemis II checking out the Moon, I've adjusted nlopes.dev homepage to show (yes, using NASA data from their OEM file) its trajectory. #rustlang #wasm #artemisii