@norootcause.surfingcomplexity.com on Bluesky

39K posts

@norootcause.surfingcomplexity.com on Bluesky

@norootcause

Lorin Hochstein Student of complex systems failures, resilience eng, cognitive sys eng. Will talk your ear off about @LFISoftware. @[email protected]

San Jose, CA Katılım Şubat 2008

5K Takip Edilen13.1K Takipçiler

Sabitlenmiş Tweet

@norootcause.surfingcomplexity.com on Bluesky@norootcause·19 Tem

I have no information about how this incident came to be but I can confidently predict that people will blame it on greedy execs and sloppy devs, regardless of what the actual details are. And they will therefore learn nothing from the details.

English

6.9K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·11h

Don't it always seem to go That you don't know what you've got 'til it's gone

Gergely Orosz@GergelyOrosz

This is more common than you'd imagine at large layoffs. Happened eg at Uber's 20% layoffs in 2020 as well. It is because layoffs are decided at Director-or-above levels, and quotas need to be hit. Directors (or above) don't have all context, and some key folks are let go. Oops!

English

1.4K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·2d

The discourse

@norootcause.surfingcomplexity.com on Bluesky tweet media

English

338

@norootcause.surfingcomplexity.com on Bluesky@norootcause·2d

@danveloper Defrag is a pretty good Decepticon name!

English

163

Dan Woods@danveloper·2d

ZXX

711

@norootcause.surfingcomplexity.com on Bluesky retweetledi

machine yearning engineer@confusionm8trix·4d

when I graduated with my stats degree I walked across the stage and shook the crusty old department chair’s hand. he pulled me in close and whispered in my ear “correlation is causation a lot of the time”

English

781

29.3K

633.5K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·2d

The consequences of being able to generate code with AI much more quickly than we can validate that code is Nature’s way of teaching us about Erik Hollnagel’s ETTO Principle. erikhollnagel.com/ideas/etto-pri…

English

1.7K

@norootcause.surfingcomplexity.com on Bluesky retweetledi

Armin Ronacher ⇌@mitsuhiko·2d

Trying to fight the slop but the slop fights back :(

English

206

10.4K

@norootcause.surfingcomplexity.com on Bluesky retweetledi

Nicky Martinez@Ncky_Mrtnez·4d

@norootcause Number 3 is becoming the most valuable one now. With AI writing most of the code, the person who can look at it and say "this will break in production" is worth more than the person who wrote it

English

@norootcause.surfingcomplexity.com on Bluesky@norootcause·4d

@johnnylavo No, I think troubleshooting is a separate skill from validation

English

John Lavin@johnnylavo·4d

@norootcause 4. Ability to troubleshoot code. Or is that what you mean by 3?

English

@norootcause.surfingcomplexity.com on Bluesky@norootcause·4d

The three skills with a lot less overlap than you’d expect: 1. Ability to code. 2. Ability to perform well in a coding interview. 3. Ability to validate code.

English

3.7K

@norootcause.surfingcomplexity.com on Bluesky retweetledi

Colin Breck@breckcs·4d

Blogged: Adapting to AI: Reflections on Productivity blog.colinbreck.com/adapting-to-ai…

English

3.1K

@norootcause.surfingcomplexity.com on Bluesky retweetledi

😈@turtlekiosk·4d

shipwright: okay so yeah i've had to replace a lot of the parts on this boat theseus: my god shipwright: calm down every single ship is like this

English

1.6K

@norootcause.surfingcomplexity.com on Bluesky retweetledi

Roman Helmet Guy@romanhelmetguy·4d

Warning: Do not adopt any new code editors this month. Beware the IDEs of March.

English

118

588

7.9K

376.3K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·6d

@isaac_flath @alexisgallagher Yup!

Isaac Flath@isaac_flath·6d

@alexisgallagher @norootcause Maybe let me llm that for you?

English

Alexis Gallagher@alexisgallagher·6d

Disagree. I suspect AI replies are often as intelligent as the input, so I’d LOVE to see raw dialogs showing how sophisticated users chat with AI. Terence Tao, using AI for math. Tyler Cowen, for econ and comment. Peter Steinberger, for development. Show me the dialogs!

@norootcause.surfingcomplexity.com on Bluesky@norootcause

Nobody wants to read the output of someone else’s prompt

English

1.1K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·6d

@prees11 Thanks for the copy-edit, now fixed!

English

Phil Rees@prees11·6d

@norootcause Great read, thanks Lorin. One typo I saw, respondres.

English

115

@norootcause.surfingcomplexity.com on Bluesky@norootcause·6d

GitHub's had some availability issues lately. Their CTO wrote a blog post with some details about recent incidents. I wrote a quick post with my reaction here: surfingcomplexity.blog/2026/03/12/qui…

English

2.2K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·6d

Nobody wants to read the output of someone else’s prompt

English

1.1K

39.7K

@norootcause.surfingcomplexity.com on Bluesky retweetledi

billy walsh@reaIityobserver·12 Mar

Never seen anything like this in all my 5 days of trading oil.

English

181

1.5K

33K

1.1M

@norootcause.surfingcomplexity.com on Bluesky retweetledi

Martin Pilgrim@MartinPilgrim1·12 Mar

The fact that most captchas are based on robots not being able to identify bikes or traffic lights doesn't fill me with confidence for self-driving cars.

English

182

2.1K

39.7K

415.8K

@norootcause.surfingcomplexity.com on Bluesky@norootcause·11 Mar

Are we at the calls for “rigor” stage of this game yet?

David Cramer@zeeg

yall are boring

English

969

Keşfet

@danveloper @johnnylavo @isaac_flath @alexisgallagher @prees11 @elonmusk @BarackObama @taylorswift13