mrekucci

Altruism is the recipe for slavery and poverty. Selfishness is the recipe for freedom and prosperity. The future is decentralized!

[mrekucci @mrekucci]

AI is Asimov's Education tape. Efficient. Scalable. Dependent on the creative minority it's slowly convincing everyone they no longer need to become.

https://t.co/cjSdnEok0c

[Addy Osmani @addyosmani]

https://t.co/jKCIAEzai7

[Mitchell Hashimoto @mitchellh]

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem.

As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)!

I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work.

It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results?

88ms => 1.5ms
150K allocs => ~500 allocs

Incredible right? Nope.

My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path.

This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput.

The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity.

Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[Addy Osmani @addyosmani]

https://t.co/ze3x7bgsL4

[Grady Booch @Grady_Booch]

I think that @DarioAmodei does not understand software engineering and that he is working feverishly to pump up the valuation of his company in anticipation of its forthcoming IPO.

[Karri Saarinen @karrisaarinen]

A common dynamic I observe with AI: it feels most impressive when you don’t know much about the subject, don’t care or don’t have a clear idea of what the you want.

This applies across design, code, legal, and more. If I don’t know code very well, every piece of code it writes feels very impressive.

Once you know what something should feel or look like, it becomes almost impossible to guide AI there. And you definitely can’t one-shot it.

[Pedro Domingos @pmddomingos]

Software sucks because those who cut corners win the race. And AI takes that to a whole new level.

[Rust Language @rustlang]

ITS HERE!!!!

Rust 1.31 and Rust 2018 is finally out! https://t.co/wbvYXA5Rar

Thank you so much to everyone who has contributed over these past three years. ❤️❤️❤️

[henry 🌘 @hdevalence]

We published a pre-release of the Bulletproofs impl that me, @cathieyun, and @oleganza have been building.

Now: composable rangeproofs, strongly-typed MPC, high perf (2x vs libsecp, 5x vs Monero).

Soon: programmable constraint system support! Read more: https://t.co/cWWJ9TDcLh

[Damian Gryski @dgryski]

"High Performance #golang" by @davecheney

Now on YouTube with a sadly nondescript and undiscoverable video title.

https://t.co/C9f6LvSbfj

[Russ Cox @_rsc]

Defining Go Modules. https://t.co/qMe3tSusx6 #golang

[mrekucci @mrekucci]

Nice debate: https://t.co/J9ATQfT2vp

[Damian Gryski @dgryski]

"Surviving Without Generics"

An experience report on building a geo package for #golang without generics and how that affected the design

https://t.co/i7zhEZqDwx

[VLªDMR 🦋 VªRNKN @tvii]

With the latest updates, pprof got a neat web UI and flame graphs right out of the box. So much love! https://t.co/iC2NeTmUrE #golang

[Brendan Gregg @brendangregg]

@jstnbckr new post: Brilliant Jerks in Engineering https://t.co/npUqguRCmZ

[Go @golang]

Go 1.9 has been released!

https://t.co/GKiU0OsYIS

Get here: https://t.co/StazJXa19M

#golang

[Google AI @GoogleAI]

Get more insight into the research done in NYC with the launch of the NYC Algorithms and Optimization Team page https://t.co/1Q54Tszd0Z

[Jaana Dogan ヤナ ドガン @rakyll]

#golang 1.9 introduces helper functions. Great for locating failing test cases if failure is coming from utilities. https://t.co/RPxTL7wuEC

[Damian Gryski @dgryski]

pprof gets an interactive web interface

https://t.co/UuNe0QyAyc