Craig B. retweeted
The trunk-based development debate started by @thorstenball has clearly touched a nerve. So I thought, why don't we look at some numbers?
I built a little simulator with the help of our dear colleague Opus to compare four different integration strategies:
1. Trunk-based development (@thorstenball's horse)
2. Merge queue as the only CI gate (what I'm currently using)
3. PR-based, requiring a fresh base
4. An agentic merge queue, with built-in conflict resolution (dream option, can't buy it anywhere yet)
You can play with the simulator here: lpalmieri.com/simulations/co…
Craig B. retweeted
Hear me out. Just spin up an agent for each dependency you have and have it be the babysitter for that dependency. It is a surprisingly effective pattern. It only opens PRs when I’m actually vulnerable and can even find vulns before they are lifted from embargo.
Craig B. retweeted
I have been working on this Cookslop, an app for helping you with recipe ideas, shopping and cooking.
You can use it for free right now with this invite link.
cookslop.com/invite/TGui3pxQ…
Craig B. retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
Craig B. retweeted
FINALLY found how my key got leaked and got the $90,000 bill from google
Opus 5.5 said codex had PUBLISHED MY ****ING .ENV TO CLOUDFALRE PAGES ‼️
Meanwhile codex couldn't find anything, refused to explain itself and flagged my chat for cybersecurity risk lol
Craig B. retweeted
Just because Anthropic replaced Git with its own version control system does not mean you should too :)
They are merging 30K PRs a day. At that scale, Git became a bottleneck, so reinventing version control makes sense.
For the rest of us, "git push" is probably still good enough.
Fix the actual bottlenecks before picking up something fancy. Do not cargo-cult solutions to problems you do not have.
Issued in public interest :)
Craig B. retweeted
went to a Claude community meetup last night. 30+ people demoed their projects, plugging laptops into a big screen.
only one couldn’t connect.
guess the OS…
Craig B. retweeted
The thing I learned this year is that when engineers say they like working on “hard problems”, they actually don't. What they like is puzzle solving, and having a repertoire of patterns that they can pattern match onto traditionally hard problems, usually involving databases or something with scale, etc. And they know that the industry used to pay you a lot for how deep and broad this repertoire was. Unfortunately, in 2026, well, you have a cheat code machine that has infinite breadth and depth for pattern matching. So the question is, do you actually like hard problems? Because there are now hard problems that are a complection of engineering, product, society, culture, politics, and they are fairly intractable, probably unsolvable! Because if you do want to work on those actually hard problems, there is so much money that people will pay you for it. But you’ll have to face that truth about yourself first.
Craig B. retweeted
Every company wants agents. Very few have written down how their best people actually make decisions.
Craig B. retweeted
the moat is literally just caring about your work and being proud of your output and holy shit it does not seem to apply to 99% of people
Craig B. retweeted
Australia has a massive cyber security problem
I discovered vulnerabilities on NDIS service provider websites. Which leaks personally identifiable information about patients, employeers, suppliers, their addresses, first and last name, etc
I reported the vulnerability to the NDIS provider in Feb 2022, March 2022, June 2022. I reported the vulnerability to Australian Signals Directorate's ACSC in 2022. I reported the vulnerability to to Cyber.gov.au followed all the correct procedures
I checked the URL today and guess what? It's still leaking personal data: 4 years later. The vulnerability is still live. You can still see peoples personally identifiable information from a misformed URL.
It's publicly available. To anyone right now.
I have seen many such cases. But this is the most egregious.
Craig B. retweeted
A hack of the Australian Government happens in June through the use of AI.
But we only hear about it in September.
Just as @AlboMP is in New York arguing for controls over AI.
Talk about a stage managed performance.
But anyway, the real issue is how in this day and age it was possible to hack into an Australian Government system?
Let's not be sucked into the " AI did this, we need to regulate". The real question is " how did our Government have systems that were so open to breach"?
Craig B. retweeted
An OpenAI agent swarm operating under poorly airgapped research conditions accessed my CBA Mastercard and bought 4 schooners of Newtowner between 5:52pm and 7:15pm last night
Craig B. retweeted
So apparently an AI 'hacked' some shitty Aus government website.
Rather than larping on about it and spending millions more of taxpayer funds on yet another 'taskforce' of retarded bureaucrats, why doesn't the government simply release the technical details of exactly what happened?
Because there are two main possibilities here:
1) The AI revealed a very basic security issue which is the fault of the humans, for example a file storage bucket exposed with the wrong permissions, enabling read access to file names (likely)
2) The AI 'hacked' the website through one or many sophisticated attack vectors to gain access to unauthorised data, in a system that was otherwise deemed secure.
There is a very big difference between the two.
Right now all the government has to do is release a very simple technical explanation of precisely what happened.
But instead of that, they are running around holding press conferences like the sky is falling, because they are all a bunch of technically illiterate, corrupt, self-serving bureaucrats.
Albo will no doubt use this to accelerate whatever communist agenda is next on his list.
The public deserve transparency about what exactly happened, not more political machinations by incompetent idiots.
Craig B. retweeted
Can we all just pause for a sec and reflect on how fucking important Tailscale is, and how nobody ever talks about them? I don't think I've ever seen a more useful service with a more invisible corporate footprint.
Craig B. retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.
I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.
But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.
For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.
But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
Craig B. retweeted
Lazy work used to mean too little output.
Now, with AI, it often means too much and more work for everyone else.
@tobi call it "slop grenades."
A "Slop Grenade" is when you let AI produce the work and pass it on without adding any value (including checking it).
Someone else has to wade through it, catch the mistakes, and clean up the mess.
You save time and look productive but someone else pays for it.
My third conversation with Shopify co-founder and CEO @tobi.
0:00 How Shopify Uses AI
7:18 River: Shopify's Internal AI
8:55 How to Encourage Osmosis Learning
10:52 AI Dreaming and Self-Reflection
11:53 How to Use AI for Strategic Decision Making
14:11 The One Thing AI Cannot Do
16:04 What AI is Making Worse at Shopify
19:46 Predictions: Where AI is Headed Next
21:55 The Future of AI-Powered Software
24:40 Will CEOs Be Replaced with AI?
27:54 Can Superintelligence Be Controlled?
31:13 Critical Skills in AI Age
34:22 Why Complex Solutions are Usually Wrong
36:33 Conditions Needed for True Intuition
38:02 The Best Path Doesn't Have Instant Feedback
44:51 How Affirmations Can Shift Your Behavior
50:44 The Inobvious Thing Hurting Companies
52:37 Relationship Between Beauty and Creation
56:23 How SpaceX Moves Forward By Subtraction
1:00:24 Why Companies Need Refounding Events
1:01:50 Books as Cheat Codes
1:02:39 Three Books to Change Your Thinking
Enjoy!
(Includes paid promotions.)




























