rjperrella

Technology enthusiast, proud supporter of the Oxford comma.

[Andreas Storm @avstorm]

McLaren got a rebrand

[Corey Quinn (in Dublin this week) @QuinnyPig]

The secret to getting off of calls you don't want to be on is to hang up in the middle of your own sentence. Only a maniac would hang up on themselves, so you must have gotten disconnected.

[Leo Laporte (twit.social/@leo) @leolaporte]

Forty years ago the first worm "escaped" containment and breached systems on the brand new Internet. It was illegal then and it's illegal now. If Anthropic and OpenAI are creating worms, labeling it "AI" doesn't let them off the hook. It's not Doom, it's Malware. Prosecute the creators, don't ban AI. "Oops" wasn't a defense for Robert Tappan Morris and it's not a defense now.

[Stéphane Graber (@[email protected]) @stgraber]

Back in March, the folks at @7aSecurity performed an audit of #Incus. The details and report are now publicly available!
https://t.co/w6F9lobqBu

[GCC - GNU Toolchain @gnutools]

Implementation of GCC's Nested Functions (vs. C++ Lambdas)
https://t.co/MD3o6CCGQ9

[Mitchell Hashimoto @mitchellh]

Beware people obsessed with outcomes instead of building outcome machines. Its worse than ever with AI, but these people existed before. Short term results above all else, etc. Don't fall into the trap. Invest in building strong fundamentals, invisible supports, and outcomes flow like water. An outcome machine.

[Commodore Computer Museum 🕹 @MuseumCommodore]

Did you know?
The Commodore 64’s three most important chips weren’t even designed for a computer.

The 6510 CPU was meant for industrial control systems.

The VIC-II graphics chip was planned for video game consoles.

The SID sound chip was designed by Bob Yannes as a synthesizer chip.

They got thrown together in under two months for the 1982 CES… and somehow created the best-selling single computer model of all time (12.5–17 million units), the platform with the biggest game library of the late 80s and early 90s, and the foundation of the demoscene and chiptune culture.

None of those chips were supposed to end up in a home computer. Yet here we are, still talking about them in 2026.

[Chuck Petras @Chuck_Petras]

All 277 issues of BYTE are available on this microfiche-inspired website created by Hector Dearman

https://t.co/ze3kKGM2fi

[Weapon 𝕏 @HellRaz0r1776]

Therapist: How do you think your OCD started?

Me:

[DHH @dhh]

In open source, you must always pay yourself first. Work on your problems, your desires. Then, once you're satisfied, help others. Anything else paves the road to burn out.

[Linas Beliūnas @linasbeliunas]

Instead of watching 1 hour of Netflix tonight, watch this ex-Google Chief Scientist Jeff Dean’s lecture. It’s the clearest explanation I’ve seen of the full AI engineering stack - from building LLMs from scratch all the way to one human coordinating 100 agents.

The best part is that it’s useful whether you’ve never touched a model or you’ve been shipping agent systems every day for the past year.

Bookmark it & watch the whole lecture this weekend, because it might end up being the most valuable thing you learn all week.

[Jen Gentleman 🌺 @JenMsft]

I don't know who needs to hear this, but if you hold SHIFT + CTRL when clicking an app icon in the taskbar, it will open that app as admin

[Leo Laporte (twit.social/@leo) @leolaporte]

@SGgrc @richcampbell and I are enjoying Threatlocker branded Guinesses at the Rí Rá Irish Pub ☘️ at Black Hat! #sponsor Sláinte!

[Joran Dirk Greef @jorandirkgreef]

Crucial to TigerBeetle’s success has been that we’re a global remote company, hiring the best people we can find, wherever we can find them.

It’s just harder to find world champion people like this, if you’re always limiting yourself to thinking with a local physical geographical mentality only.

The world of software, “the digital frontier” is invisible, without borders.

However, sometimes, a kind of restricted physical thinking arises as a reaction to conflating “remote” with “work from home” or “culture” with being in “the same room”.

Yet, “remote” and “work from home” are not the same, and a strong corporate culture in the long term can never sustainably depend on everyone being in “the same room” (that doesn’t scale!).

For example, many of our team work from small offices, not from home. And our culture is not “where we are”, but “who we are”, the deep intrinsic values we all share.

Therefore, we’re remote, and don’t over-specify that we require physical proximity to function.

Rather, just as the distributed systems we design are best designed logically, not physically, so too the organization we design at TigerBeetle is designed logically.

[Branko @brankopetric00]

Push three times in a row and GitHub Actions runs three full pipelines. The first two are already dead.

Add this and it kills stale runs automatically:
concurrency:
group: ${{ github.ref }}
cancel-in-progress: true

Less wasted minutes and faster feedback on the commits.

[Zlatan Ibrahimović @Ibra_official]

The studio will never forget

[Mitchell Hashimoto @mitchellh]

My heuristic is that any diff an agent generates over ~1500 lines is too big and is indicative that the problem needs to be decomposed. This is my general pattern now for feature work:

1. Try to implement the whole feature, loosely guided. I call this the "draw the owl" prompt in reference to the meme. Expect garbage, you're going to get garbage.

2. If the diff is less than 1500 lines, review it and iterate normally. If the diff is more than 1500 lines, prompt the agent to decompose the problem into atomic, incremental, reviewable tasks. Simultaneously, do this yourself.

3. Agents will very often make these tasks way too specific to the shape they solved. You need to massage it into the right general shape. Do that.

4. Kick off new agents to work on those incremental things (as parallelized as possible). Apply the same rules.

5. At a certain, point, repeat the "draw the owl" prompt. At some point, you will get beneath your review-ability threshold.

This has been producing consistently high quality, maintainable, reviewable chunks of code that have a good handoff to either merge as-is or human refinement.

And with the latest frontier models at xhigh thinking, these are all slow enough that you can usually have multiple going concurrently while you are actively reviewing others or working on your own tasks.

HITL (human-in-the-loop) agents are still super important, especially for feature work. Features touch the human boundary in terms of UI, API, etc. And net new stuff can introduce pathologies in the architecture that violate desired invariants (these should be represented in specs or tests but we aren't perfect!).

I know a lot of the leading edge agentic discourse is about "loops" and agents driving agents continuously. I do some of that (will report on that later). But, in terms of raw daily get-shit-done type of work, this is my most rewarding pattern at the moment.

[7 Days to Die Official @7DaystoDie]

TFP is proud to announce the 3.0 Dead Hot Summer Developer Stream is this coming Wednesday, June 10th at 9 PM CT. Join TFP Co-Founders Richard & Joel Huenink & TFP Senior Programming Technical Lead Lathan as they dive into the changes coming to 3.0.

https://t.co/ItUvIXQ6DI

[Uncle Bob Martin @unclebobmartin]

I start with very informal specifications written by hand. I have an agent convert these into harder specifications that are subdivided into tasks. I review these.

Then I feed those tasks into the specifier agent, which converts each task to Gherkin, prunes the Gherkin, and then hands it off to the coder agent. I spot check the Gherkin.

The coder agent writes acceptance tests directly from the Gherkin. Then writes unit tests. Then writes code. When all those tests pass, the coder agents hands off to the refactorer agent.

The refactorer agent reduces crap to 6 or below, and reduces any duplication. Then it write property tests and gets them to pass. Then it hands off to the architect agent.

The architect agent runs language mutation and covers any uncovered sections, and kills all survivors. Then it runs Gherkin mutation and kills any of those survivors. Then it runs the entire test suite, and when it passes it hands the result off to the specifier, coder, and refactorer.

I spot check the code.

This is an exercise of transformations from the informal to the formal through managed stages, with human interaction decreasing with each stage.

Raw computer power is the limiting factor. Those mutation tests are CPU intensive.