Patrick Laughlin
42 posts

Patrick Laughlin retweetledi

Love it. Now imagine a world where new macs weren't held hostage by macOS.
vogel@ryanvogel
I don’t know how to explain it but this just looks right Omarchy 🤝 Mac Pro
English

@sssmcgrath github.com/ChrisTitusTech… seems like a good first step?
English

@nicbarkeragain Damn. Never thought of it like that. Big true.
English

I broadly agree here but there’s also another mechanism at play - the models take so long to respond that it raises the floor for what is considered “slow”. Advent of the web raised this bar from ms to seconds bc of network, and now LLMs are raising it to 10s of seconds.
Mitchell Hashimoto@mitchellh
I think one of the funniest things is how frontier labs spout how AI is writing their code, but the reality is that the products they ship are buggy, resource hungry messes. It's kind of the worst advertisement ever for both their products and their worldview.
English

@typecraft_dev Make a few fidget spinners and then let it collect dust for years.
English

@BasNorth @LowLevelTweets @ChShersh The skill: having read Computer Systems: A Programmer's Perspective
English

@cnlohr I’m about two weeks into working without LSP and all autocomplete off and it’s pretty liberating. Uncomfortable at first, but the familiarity and memory starts compounding.
English

Watch this, listen to what he says about the economics of software development. Software is going to change a lot in 2026.👇
geoff@GeoffreyHuntley
ralph from 1st principles youtu.be/4Nna09dG_c0?si…
English

@thdxr A few off the dome
Pin presses
Rack pulls
Pullups without wobble
Band pegs
Dumping the rack is impossible
Pulldown/row attachments
English


@geoffreylitt Really interesting idea. My only concern is that this presupposes the tutorial is correct, no? Have you begun building only to find it is incorrect?
English

I cannot emphasize enough how much I prefer this "tutorial doc + build-it-yourself" coding workflow to the typical "ugh" feeling of reviewing huge agent PRs. You can try it right now and see for yourself:
1) Instead of having Claude Code make a PR, ask it to output a Markdown doc with a deep, detailed guide for a dev to implement the change, including teaching you background and context about the broader surrounding system, and rationale behind why we're doing things a certain way. Tell it to be very exhaustive and ultrathink. (The result should be go way more in-depth than a typical plan mode output, it may take a while so I tee this up well in advance)
2) Read the resulting doc. And then code it yourself! Use Cursor to go faster: tab complete is your friend. You can also use the Composer model in Cursor Agent to fast-forward thru tedious bits -- but avoid using slower models or doing too much AI work at one time. You are staying connected to the work and going step by step. Think about it as you go, correct course as needed. Go off-script from the tutorial doc whenever you want.
What I find when I do this is that I'm able to reactivate the "building things manually" parts of my brain which help me make good decisions and understand what's going on, but I'm also able to go super fast with the AI tools.
Geoffrey Litt@geoffreylitt
on to my next task! following the tutorial guide claude precooked
English

@MainMeowMix @thdxr @dizzzmas Is anyone using aerospace successfully with multiple monitors? I can’t seem to figure it out
English



















