Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
I must admit that nothing about computers, since I'm in love with the field, was so uninteresting as the Javascript different fashions, waves, frameworks, rewrites, hypes. And I'm one that loves almost every shit programming related.
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.
>1/3rd of Framework Laptop 13 Pro customers are buying it to replace a MacBook Pro, and almost all of them are switching to Linux (based on our optional post-purchase surveys).
Introducing Claude Opus 4.7, our most capable Opus model yet.
It handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back.
You can hand off your hardest work with less supervision.
Toggle switches for changing temperature?
Toggling it zillion times to get to the right temp. Or if you probably hold it, it'd accelerate and go past the target. All while requiring constant attention.
Temp is a fixed range, needs a knob with hard stops at Min/Max. The hard stops signal that you've maxed out without looking. Changing from cold to hot takes less than a second. Precisely adjusting temperature is also straightforward and fast.
Fan speed should also be a knob with strong fixed detents. Fan speed knob should be of different shape than temperature.
Introducing Project Glasswing: an urgent initiative to help secure the world’s most critical software.
It’s powered by our newest frontier model, Claude Mythos Preview, which can find software vulnerabilities better than all but the most skilled humans.
https://t.co/NQ7IfEtYk7
Turns out, it just wasn't obvious to me. Blown away by the run @matthuang, @gakonst, and the @tempo have been on over the last 6 months.
Makes you wonder what they can do with another 6 👀
I believe we've found the best AI-native coding interview
We call it the “Composer 1 interview”
Candidates get 1 hour to build a real, medium-sized project live
The only constraint: they have to use Cursor’s Composer 1 model
Why don’t they just tokenize the oil in the Middle East and transport it across permissionless financial rails, thereby avoiding the Strait of Hormuz altogether