
A lot of cybersecurity problems are really organizational dysfunction problems hidden behind a layer of tech. No amount of AI tokens can fix that. Feel free to send this post to your boss.

Observing the universe into existence one light cone at a time. Board member erlef.org creator grisp.org grisp.io Erlang, BSD, Physicist.

A lot of cybersecurity problems are really organizational dysfunction problems hidden behind a layer of tech. No amount of AI tokens can fix that. Feel free to send this post to your boss.

What did he know…
It's 2027 in the Bay Area. You take a driverless Uber to the polyamorous meetup to chill with your bros. 40% of attendees have the measles

Ok, this is neat! Someone reported a bug that Elixir's Task.ignore/1 could leave messages in the caller's inbox. Reproducing it was tricky, out of 1.2M attempts, it only leaked 52 times: github.com/elixir-lang/elixi… Therefore, to consistently "reproduce" the issue, I wrote a property in Lynx (@leanprover + @elixirlang) that Task.ignore/1 should not not leak messages: github.com/josevalim/lynx/bl… Of course, we could not prove this property to be true, because there was indeed a bug! And once we fixed the bug, the proof validated, showing that Task.ignore/1 no longer leave trailing messages in the scenarios dictated by the property. Hooray!

the problem with all LLM meta conversations: people who dont have the skills claim it removes the need for skills people who do have the skills will tell you its a productivity multiplier they're both right, but one is far more correct

The weird thing about vision is if you tell most people the long term vision up front they call you crazy and laugh at it. It's better to do something short term and obvious that everyone can grasp while carrying water and chopping wood towards the real vision.


I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted. It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different? Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable? Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.

“You cannot get a simple system by adding simplicity to a complex system.” — Richard O’Keefe

You don’t need to be liked, but you do need to be respected. Nothing kills your authority faster as a leader than losing it. When things are falling apart your team should know you'll stay calm, work harder and longer than they will, and do it with a smile on.

Hey @johnternus hope this gets through your filter. Microsoft did something stupid like this when I worked there. Steve Ballmer apologized to the company and fixed the problem. He got my loyalty by doing so. Hope you can pull inspiration to fix this problem from his leadership.
If you have an Apple developer account or an app in the App Store, read this now and share it. Apple rejects your app. The notice is vague, so you fix what you reasonably think is wrong and resubmit. Apple approves it. Months later, with nothing in review, Apple terminates your account under 3.2(f) for “a pattern of manipulative or misleading behavior.” Every app gone. No explanation of what you did. Your crime? Trusting the approval. Apple’s own reviewer looked at your fix, with your rejection history in front of them, and said yes. Then Apple turned that yes into evidence against you. So who’s misleading whom? I ran App Review for seven years and wrote the guidelines. 3.2(f) used to mean real fraud. Now it’s being used against developers who did exactly what Apple approved. I’ve made this Substack post free for everyone. Every developer needs to see it before this happens to them. Share it before someone you know gets that email. phillipshoemaker.substack.co…

If you have an Apple developer account or an app in the App Store, read this now and share it. Apple rejects your app. The notice is vague, so you fix what you reasonably think is wrong and resubmit. Apple approves it. Months later, with nothing in review, Apple terminates your account under 3.2(f) for “a pattern of manipulative or misleading behavior.” Every app gone. No explanation of what you did. Your crime? Trusting the approval. Apple’s own reviewer looked at your fix, with your rejection history in front of them, and said yes. Then Apple turned that yes into evidence against you. So who’s misleading whom? I ran App Review for seven years and wrote the guidelines. 3.2(f) used to mean real fraud. Now it’s being used against developers who did exactly what Apple approved. I’ve made this Substack post free for everyone. Every developer needs to see it before this happens to them. Share it before someone you know gets that email. phillipshoemaker.substack.co…



Jean-Luc Picard remains the single most compelling vision of progressive politics I am familiar with — secular, rational, compassionate, egalitarian; a believer in progress & abundance but also duty, hard work, and a constant battle for self-improvement and improving the world.


SIR PATRICK STEWART (1940-2026) Before everything else, Patrick was defined by being born and bred in Yorkshire, the proud county in the north of England which he loved to the end. You could hear it in his accented voice and in the stern honesty with which he told you what he thought and felt. Yorkshiremen have no truck with half-truths or avoidance of big issues. He wore his heart on his sleeve, which made him a man to rely on, to admire and in my case, love. We first met as ambitious young actors with the Royal Shakespeare Company half a century ago but we weren’t in the same productions. My first strong memory was a few years later, meeting him in the street in central London when he told me about an offer to take over a leading part in 'Star Trek'. “But Patrick think of your stage career in the UK. Do you really want to risk—getting lost in Hollywood for years and years?”. Well, he took the risk and thank goodness for us all that he did for not just his devoted Trekkies but film and theatre audiences, who marvelled at his using international celebrity to star in a string of cinema successes ('X-Men' of course) and in great classical plays by Shakespeare, Ibsen, Arthur Miller, Peter Shaffer, Pinter and Beckett at Stratford-upon-Avon, in London’s West End and on Broadway. America was his adopted home, where he met his adored Sunny who has cared for him through sickness and health, through thick and thin. But he never forsook his origins: and the proudest achievement of the most respected and beloved actor of his generation on either side of the Atlantic, was his appointment as Chancellor of Huddersfield University in Yorkshire. His farewell performance in 'Avengers: Doomsday' is yet to be seen. Ian McKellen 29 October 2026 Photo: University of Huddersfield