AgentSee Podcast

AgentSee

James Hartt and Abrar Mahmood are building a software agency from the ground up, in public, with agents doing the work. Every agency was organised around one scarce thing, engineering time, and that constraint has moved. Each episode is what they actually did, what it cost, what broke, and which of their stated questions it touched.

Episodes

  1. 5d ago

    Twenty questions before you build

    James and Abrar go through the twenty questions before you build, a group of four at a time: the idea, the care a domain needs, the conditions it runs in, its shape, and who owns it once it exists. Code is a byproduct now, so the questions are where the thinking goes; a regulator changes the build and keeping up with one is work of its own; scale that never arrives slows you down and scale that does sets fire to things; offline is the requirement that arrives at the eleventh hour; and somebody has to be able to restore the backup. It ends with the brief, the things they insist on for every build, and a flood of CVEs. Chapters: 00:00 A toy from the playground, and twenty questions01:59 Where it came from: code as a byproduct03:36 The idea: what should it do, and for whom06:59 Care needed: the regulator, and keeping up with it11:35 Running conditions: the busiest day, uptime, platforms16:01 Offline, the requirement that arrives at the eleventh hour20:37 Shape: AI inside it, how often it changes, what must never happen25:04 What an offline flow looks like: pen and paper26:36 Owning it: worth it, signed off, and looked after by whom30:57 The brief, and what we always insist on32:15 Security: a flood of CVEs, and vibe-coded targets33:55 A small team that can do what a giant one could35:54 Wrap: a bit of whimsy, and guests from here on36:51 Outro Mentioned: Issue No. 7: Twenty questions, and the one that counted was the twenty-firstThe twenty questions, to run in your own assistantThe skill file itself, in the openCVE, the vulnerability catalogue the flood lands in Of the questions on the site, this one touches: 1. If writing the code is no longer the expensive part, what is the client actually buying?3. What is a product manager when the specification is executable?4. Who is accountable for a system that nobody typed?5. How do you run acceptance testing on something produced faster than a person can read it? AgentSee is two people building a company in public, with agents doing the work. https://agentsee.work · hello@agentsee.work Subscribe: https://agentsee.work/podcast/feed.xml

    Twenty questions before you build
  2. Nov 3

    Vibe coding, and the rise of the product engineer

    Abrar builds GradeDrive, an AI marking tool for schools, with a non-technical co-founder, and helps a second startup where the product team ships its own ideas. He explains what makes that safe: a skill that gives every idea its own worktree, database and dev server, a read-only environment the agent can be trusted with, guidelines written after a feature that ran a whole class's PDF in the browser, and a draft pull request that spins up an environment of its own. James asks about native apps, things going off the rails and what the job is now. The answers: web is easy and native is not, it is easier than ever to build sloppy stuff, taste still comes from people, and Abrar has not opened a code editor in six months. Chapters: 00:00 GradeDrive, and another startup01:36 How it used to work: idea, engineer, ticket, wait04:10 Vibe coding: quick, motivating, throwaway07:15 Prototypes that carry the intent10:28 Enablement: a read-only environment, a worktree per idea14:43 When a vibed feature went wrong19:00 Agents that check their own work in a browser21:42 Web is easy, native is not26:25 One-shotting a feature, and the draft pull request30:06 Easier than ever to build sloppy stuff34:43 Engineering is enablement; then gravitate to product37:40 Coding is an abstraction; taste is still ours42:11 The role is exhausting: the thinking comes first47:34 Where people hit the wall52:10 Outro Mentioned: GradeDrive, AI marking for schoolsClaude Code, and the Claude desktop app the co-founder usesgit worktree, one checkout per ideaDraft pull requests on GitHubThe Ralph Wiggum loopExpo, the native app toolchain mentioned Of the questions on the site, this one touches: 3. What is a product manager when the specification is executable?5. How do you run acceptance testing on something produced faster than a person can read it?7. What does taste mean when volume is free?8. Do engineers still want the job? What is it now — author, reviewer, director, or something we don't yet have a word for? AgentSee is two people building a company in public, with agents doing the work. https://agentsee.work · hello@agentsee.work Subscribe: https://agentsee.work/podcast/feed.xml

    Vibe coding, and the rise of the product engineer
  3. Oct 27

    Running our own mail server, on purpose

    James set up AgentSee's own mail server on a Swiss VPS, with an agent writing the OpenTofu and most of the configuration: two afternoons' work rather than the weeks it would once have taken. Abrar asks what was hard, and the answer is the click ops inside Stalwart's admin panel, a CLI that was not built for an agent, buttons the model insisted existed, and making the result reproducible afterwards with a snapshot script. They also cover borrowing sender reputation, the monitoring that is not built yet, whether either of them would recommend this to a client (no), and what it is like to let an agent drive the browser. Chapters: 00:00 Why mail at all02:15 The alternatives, and why Infomaniak05:56 OpenTofu, and what the agent wrote07:26 Stalwart: the click ops and a clunky CLI12:31 Buttons that don't exist, and the snapshot16:40 Set and forget: spam, SES and the relay19:00 Monitoring, and what we have not built21:56 Reputation: borrow someone else's23:51 What the server holds25:48 Would we do it again?29:53 Letting an agent click36:53 Where to find it all38:00 Outro Mentioned: Issue No. 2: the mail server, written upThe infrastructure, as OpenTofu, on GitHubStalwart mail serverOpenTofuInfomaniak Public CloudSMTP2GO Of the questions on the site, this one touches: 4. Who is accountable for a system that nobody typed?8. Do engineers still want the job? What is it now — author, reviewer, director, or something we don't yet have a word for? AgentSee is two people building a company in public, with agents doing the work. https://agentsee.work · hello@agentsee.work Subscribe: https://agentsee.work/podcast/feed.xml

    Running our own mail server, on purpose

About

James Hartt and Abrar Mahmood are building a software agency from the ground up, in public, with agents doing the work. Every agency was organised around one scarce thing, engineering time, and that constraint has moved. Each episode is what they actually did, what it cost, what broke, and which of their stated questions it touched.