Linkedin

Do trust and accountability go hand in hand? This is something I’ve been chewing on over the weekend. And I don’t know really, but here’s where I’m coming from. One of my side projects at PiForge at the moment is building a system around Agentic Engineering using team lead principles I’ve honed over years, and applying how human teams communicate and organize over the SDLC to agents (i.e. start with a spec, write tickets on a kanban board, grab the next highest priority, work till done, test, PR, release, document). ...

Just because your fancy new Claude Code plugin prints out “50% tokens saved” in the logs doesn’t mean you actually got them. I was playing around with Caveman Compression last week and tried to get the UserPromptSubmit hook to rewrite prompts using the tool for savings across the board. Turns out? The hook doesn’t allow it. Probably for security reasons; can you imagine the injection attacks if any random plugin could hook into and replace your prompts? ...

That’s the punchline and the problem. I’ve run into these two similar scenarios which have had me stumped and annoyed. In one, I’m running Claude Code in both GoLand and PyCharm, trying to integrate one project’s API with another project’s GRPC service. In the other, I have a Scala library that needs updates, and then multiple services that depend on that library. The hiccup: each instance is completely unaware of the other’s existence. ...

Trigger warning: This post contains opinions. Specifically mine. It also contains a confession or two, which I’m not thrilled about, but here we are. I don’t have many people in tech I actively look up to. The industry is drowning in loud, obnoxious voices who are very good at having opinions and very bad at having done anything. But Carmack is one of the rare exceptions. He’s always been the quiet, thoughtful one. The hacker in the original sense; someone who understands systems deeply enough to bend them, who ships because building is the point, not the clout. I’ve written before about my own struggle with that identity vs. the need to actually make money, that tension between doing the craft and doing the business. Carmack, for most of his career, has never had to compromise on that. He gets to just build. ...

Around a year ago I started one of my blog posts with this musing on “The Promise vs. Reality of AI in Tech”: I’m concerned about the industry’s direction with these [improvements in AI]. Instead of creating better developers, we’re often replacing them. Rather than building amazing accessibility tools, we’re creating deep fakes and virtual companions. Instead of developing better MVPs for real problems faster, we’re seeing low-quality products marketed as revolutionary simply because they were built without coding experience, for no purpose other than a quick cash-grab. ...

We spend more effort learning how to prompt LLMs than we do communicating with other humans. People complain that AI is bad at understanding humans, but in truth, humans are rediscovering how bad we are at explaining ourselves. Prompting works because you’re forced to do interface discovery consciously. You test phrasing, observe outputs, refine assumptions. With humans, we think discovery is rude or inefficient, so we skip it. Then we’re shocked when the call fails. ...

This came up in my feeds today. I’ve said it before and I’ll keep saying it until I can’t anymore: never before has there been a time where we needed to be more intentional about training and mentoring juniors than now. As much as I love and use it, my biggest worry with current AI tooling has always been that it takes the thinking and understanding away from you. This is different from previous coding tools. Many just obfuscated or abstracted concepts, others assisted with tedious tasks, but this time the tool does it all. And it’s making us lazy, and it’s making us less capable. Studies are starting to show this. ...

The words we choose matter. People have been calling me pedantic for a long time, but I’ve never seen the problem with that. Words have particular meanings. Even synonyms are just “similar”, not usually the same. Some time back I wrote a blog post about “Why You’re NOT an Engineer (also Why It [Probably] Doesn’t Matter)” The key point I made: there IS a difference between a coder, a programmer, a developer, and an engineer (although some people disagreed). ...

I’m really happy to see my LinkedIn feed finally catching up with what I’ve been saying for the last nine months: vibe coding sucks, and fundamentals are important. Also, before the haters go and hate, “all vibe coding is coding with AI, but not all coding with AI is vibe coding”. My dislike is and always has been with “the vibe”. I’ve been reading books like Masters of Doom and Hackers: Heroes of the Computer Revolution lately, and looking back at those pioneers, they didn’t just have an intense love for what they did, they had a crazy deep fundamental knowledge of the things they worked with. And if they didn’t understand something? They took the time to figure it out. ...

One of the hardest lessons I’ve learned in tech is boundaries. When to set them, how to enforce them, and (occasionally) when to cross them. Learning this early in my career made it easier to apply later – like now, running my own business. If I don’t get paid when I don’t work, then I don’t work when I don’t get paid. Simple. But this isn’t just on my mind because I’m chasing overdue invoices (though, you know, that too). It started when I saw posts and articles about how 996 culture is gaining traction among startups and founders, especially in Silicon Valley. You know, the “work 9am to 9pm, 6 days a week” grind. And this is despite most people knowing it’s unhealthy. Despite the constant complaints on social about burnout and not having a life outside work. ...