There should be a rule that “nit: …” PR comments are only permitted when you review promptly.

I’m more interested in when it will stop lying about tools that it doesn’t have than when it will acquire the tools.

This is good but I would hope for better. There are a lot more things than weapons that shouldn’t be fully autonomous with current models. But that can’t be said without damaging the hype so that’s all we get.

Have people started saying “ralphable” yet? “Yeah that sounds hard, but it’s ralphable”

And your reply made a difference for me. ❤️

I’m talking to myself as much as anyone else here. I tend to lose touch with this when the environment around me gets hectic.

It’s still a marathon, not a sprint.

Ignore extreme takes. Stay curious. Keep learning. Keep working. It’s going to be OK.

And doing it well still requires skill. And the skills still require curiosity, time and effort to acquire.

But it’s not a free ride. You still have to exert effort to produce valuable things. And you are still responsible for the quality of your work.

Rising abstraction is the gift that keeps on giving. You can now produce things of value without spelling out every line of code. This does not replace you, it empowers you.

Your task was never to produce code, it was to produce things of value.

Lines of code produced was always a bad metric but it is now officially and forever removed of any and all meaning. Good riddance.

🤣

One of the critical things that distinguishes a senior developer from a junior developer is an understanding, deep in their bones, that the cost of DOING a thing is cheap compared to the cost of truly FINISHING a thing and utterly trivial compared to the cost of MAINTAINING a thing. Like 1:10:10000.

I wonder what Geoff thinks about this.

Fabulous Adventures in Data Structures and Algorithms - Eric Lippert Author Eric Lippert introduces fabulous solutions using uncommon algorithms and data structures. There’s a lot more to algorithms than the useful-but-boring recipes you recite for every interview. Th...

I'm writing another book, and the first few chapters are available through Manning Early Access now! For 50% off!

hubs.la/Q03Q9PGP0

More details, and the story of how I came to write it, are on my blog at

ericlippert.com/2025/10/30/i...

It feels great to be writing again after a long break. :)

`IMemoryApartment<T>` was right there.

I find it funny that when you're done with a rental from a `MemoryPool`, you dispose the owner.

I need an update to the classic xkcd cartoon where "Agent is agenting" replaces "My code is compiling!"

Copilot: "Let me read lines 1-50... Ok, let's read some more lines..."

Read the whole file, bro, you're a computer!

I’m sorry to hear that. Put your health first and take a break if you need it.

I think somebody vibe coded floating point where it has no business being used at fidelity.com.

I have 0.0003 shares of MSFT now.

I had to subtract $0.01 from amount shown “available to withdraw” for it to stop saying “you don’t have enough cash”. 🙃

My favorite video game is typing things into this box and then erasing it because I realize nobody will care.

If you do this, you can also remove `internal IntPtr Handle => this.handle;` which you'd no longer need. It's basically DangerousGetHandle() without the scary name, but it deserves the scary name. 😊

Cool demo of the problems! I think the solution can be improved further.

P/Invoke signature can be changed to use RocksDbSafeHandle instead of IntPtr. Then you wouldn't need GC.KeepAlive. P/Invoke will marshal SafeHandle for you and handle keeping it alive for duration of call.

Wow! Congratulations!

Foo(Bar());

Code review: LGTM
—
var x = Bar();
Foo(x);

Code review: The type of ‘x’ is not apparent, don’t use var here.
—
Please explain to me how these are different. I legitimately don’t get it.

The people who think they are good at everything because they are good at coding are also bad at coding.

🤮