Aaron Kardell

This takes me back to the Multics design point from the 1960s -- the primary interface is the API. It's frustrating to me that this lesson has been forgotten. The API is there behind the curtains but is not really useable as an API. In plain language, the big change is that we now have the tools to make everyone a "programmer" -- but what do I mean. And as I wrote in rmf.vc/IEEEAboutSoftware, we've been trying to remove intermediaries going back to Fortran. AI has empowered people, but we need to teach the concepts of software rather than the mechanics of coding. It is about having the understanding to discuss your intent rather than just coding it once or using what has been provided.

10

1 Comment

I just bundled everything into one. Claude Code setup. OpenClaw agent setup. AI supervision system. Screen recorder. Four guides. One stack. The full picture of how I run an AI-operated solo business without watching every step. Individually these are $88 worth of material. I'm releasing the bundle at $37 for the first wave. Here is what is inside: Complete OpenClaw AI Agent Setup — full install, browser relay fix, custom model config, 9 agent skills, operating playbook Claude Code Autonomous Agent Setup — PRD template, stable project structure, ACP command pattern, log supervision, 6 failure fixes AI Agent Supervision System — heartbeat overlay architecture, idle-only monitoring, PRD-first workflow, revenue loop design AI Screen Recorder for Claude Code — one-prompt 60fps demo videos, auto-zoom, dead time removal, zero manual editing If you are building toward a business that runs without you, this is the full stack. Link in my profile.

1

Give two engineers the same requirement, and they can still build two very different features. I've noticed that the difference often comes down to how much context they have. Take a simple requirement: "Build a feature that lets users upload a file." With just that requirement, an engineer is likely thinking about: → How should the upload work? → Where should the file be stored? → Which file types should be allowed? → What happens if the upload fails? Now add some context. The user is a salesperson sitting with a client. They are uploading a document from their phone during a meeting. They need to know immediately whether the upload worked because they need to move to the next step. The questions suddenly change: → Does this need to be optimized for mobile? → What happens on a poor internet connection? → Should we show upload progress? → What happens if the wrong file is selected? → Should the user wait for the file to finish processing? → What should happen when something goes wrong? The requirement hasn't changed. It's still just: "Upload a file." But the way the engineer approaches the problem has changed completely. And this is where context becomes really important. A requirement tells an engineer what needs to be built. Context helps them understand why it needs to be built and how it will actually be used. That context allows an engineer to make better decisions without needing someone to define every possible scenario upfront. The best engineers don't just ask: "What do I need to build?" They also ask: "What is the user actually trying to accomplish?" That's the difference between implementing a feature and actually building one.

22

2 Comments

A helpful takeaway from my conversation with Josh Sorenson: development teams should be thinking about how to empower more people to prototype. The prototype can be rough, the point is momentum. Then the dev team can translate it into planning documents and rebuild the solution properly from scratch.

4

Eric Ries spent months writing the code at the heart of his startup's original strategy - the software that let his IM avatars interoperate with other messaging networks. Almost all of it got thrown out. Episode 3 of TheBuildFramework just went up - Chapter 3 of The Lean Startup, on why "we learned a lot" is usually just an excuse, and the concept Ries built to fix that: validated learning. The story that anchors it is IMVU. Ries and his cofounders had a strategy they could diagram on a whiteboard - network effects, switching costs, all of it. Customers didn't care. They tore the strategy apart, meeting after meeting, until it became clear the whole premise was wrong. When the pivot came, the interoperability code Ries had personally built was discarded. He asked himself the question a lot of builders avoid: would the company have been just as well off if he'd spent those months on a beach instead? The answer he landed on is the part worth sitting with - work isn't wasted because it was deleted. It's wasted when it doesn't produce validated learning about what customers actually want. IMVU also introduced Ries to "the audacity of zero": the uncomfortable truth that investors and advisers found it easier to have faith in the company when it had no revenue at all than when it had a small, real number ($500 a month, in this case). Zero invites imagination. Small numbers invite doubt. Full breakdown is live now. Link's in the comments - curious whether the "audacity of zero" idea matches what you've seen with early traction (or the lack of it).

2

1 Comment