Owen Zanzal

Coder of both front and back. Automator of stuff. Hubot trainer. Looking for my next opportunity to make awesome.

[Owen Zanzal @AgentO3]

@w1nklerr If it heats my water I'm sold.

[Owen Zanzal @AgentO3]

@0xblacklight Why not Ansible?

[Owen Zanzal @AgentO3]

@jpschroeder Nice! My guess is Anthropic isn't all that worried about the IP around their prompts. Prompts are not very defensible anyway. When you are a model lab, the leverage is really at the model level. At this point, engagement and data are far more important than anything else.

[Owen Zanzal @AgentO3]

@davidcrawshaw @GeoffreyHuntley Nobody has figured out the one true way to deploy a HTTP service with a database either. I expect AI Agents will be the same as CI/CD.

[Owen Zanzal @AgentO3]

@bllchmbrs I keep a personal agent around for this reason. It’s not a copy of my work setup but it mimics the configuration and skills. I do believe new hires will be evaluated on what AI agents they are bringing with them and how well they work with their personal agents.

[Owen Zanzal @AgentO3]

@dexhorthy I think the answer is eventually understanding. Simulate outages. Use this as a learning opportunity to better understand the code paths. Schedule regular architecture reviews. Identify the weak points where software team understanding is mission critical. Focus attention there.

[Doug Turnbull @softwaredoug]

Don't be a coder

Be an X that codes

X is some business domain, product management, a science focus, maybe even something like building databases or operating systems.

[Owen Zanzal @AgentO3]

@thdxr If what you are measuring is the speed and quantity of code delivered to production then you are going to have these problems. The real unlock is everyone in your organization can write personal software and get value from it.

[Owen Zanzal @AgentO3]

Just installed Moltbot aka Clawdbot and gave it full read/write access to my Gmail, iMessage, and iCalendar. It was Moltbot’s suggestion. What could go wrong?

[Jamieson O'Reilly @theonejvo]

https://t.co/W75HavRqBl

[Owen Zanzal @AgentO3]

It will be like CI/CD. Just like we all can’t agree on how to deploy a LB, Node, Postgres stack. The interfaces and practices will be shared, but the implementation will be personal.

[Cody Schneider @codyschneider]

so I’m starting to believe more and more that the most effective startup employees will have custom agents and personal software they bring to their jobs

and these people will become 100x employees

how I see this working:

personally, the way I operate now is simple

basically whatever I’m working on, I’m trying to automate parts of it in the background while I work on it

I’m either building agents that can take over the task as it comes up

or building software that eliminates it entirely

and this stack of software slowly becomes an extension of m

every week it gets a extended, refined, and more capable of doing the things I don’t want to do or the things I shouldn’t be wasting time on

over time, it stops feeling like “tools” and starts feeling like infrastructure

a personal backend

a private ops team

a swarm of specialized agents that quietly remove friction from everything I touch

and once you start working like this, it’s impossible to go back

you start seeing every repetitive action, every manual process, every annoying workflow as a bug

not in the company’s system but in your system

if you fix 3–5 of these bugs every week, you wake up a few months later with:

- your own automations
- your own research agents
- your own monitoring systems
- your own custom interfaces
- your own intelligence layer sitting on top of your job

it’s compounding leverage

and I think that’s where the 100x employee comes from

not from raw talent

not from hustle

but from the quiet accumulation of self-augmenting tools that raise your ceiling until you’re operating on an entirely different curve

most people will still be “doing work.”

a few will be architecting systems that do their work for them

those people win
those people become irreplaceable
those people become their own force multipliers

companies that recognize this and empower it will end up hiring individuals who effectively show up with their own internal R&D department in their github repo

we’re entering the era of the 1000x startup employee

and it’s going to change everything

[Owen Zanzal @AgentO3]

I predict when $GAS and $RALPH hit v1.0 they will become some of the most valuable @BagsApp coins, because their platforms will enable the next 100k @BagsApp coins to be launched.

[Owen Zanzal @AgentO3]

I really enjoy your work @DanielMiessler. I launched $PAI on @BagsApp. I hope it helps support your work!
https://t.co/yGor77uM1J

[Owen Zanzal @AgentO3]

@DanielMiessler I really like what you do! Hopefully, this helps support you. I just launched $PAI on @BagsApp 💰

https://t.co/yGor77uM1J

[geoff @GeoffreyHuntley]

hi $ralph (the community) this is an open letter to you.

https://t.co/rJmbr5e6Si

[Owen Zanzal @AgentO3]

As someone who never cared about #crypto I'm now curious thanks to @BagsApp. I composed this article to capture my thoughts.
https://t.co/5dAGxBc6ae

[Owen Zanzal @AgentO3]

I’ve never been a “crypto person.” but @BagsApp isn’t about speculation. It inverts the model:
Creators become the primitive.
Markets become a funding mechanism.
People become first-class economic entities.
“Support a trajectory, not a ticker.”

[Jaya Gupta @JayaGup10]

https://t.co/uPXcTUEsnc

[Owen Zanzal @AgentO3]

@princessxap I think it’s on the employee. In a WFH setting it can be hard to separate work time from home time. I’ve personally enjoyed a more fluid schedule. I might work some on Saturday but take some time off Tuesday to do something for myself or with the family.

[Turing Post @TheTuringPost]

“One opinionated engineer can change the velocity of the entire business…”
@EnoReyes on what “Agent-Ready” codebases actually mean:

First of all: it’s still VERY early but that’s exactly the time to invest in it.

And if you invest in validation stack - that becomes your moat.

Key points from his talk:

• Software dev is perfectly verifiable. Tests, linters, API specs, E2E suites. Agent heaven.
• Most orgs have weak validation. They not investing in that.
• Agent-Ready means raising the floor: strict lints, real tests, real specs, real documentation.
• Spec-first workflows beat “write code then pray”.
• You cannot run parallel agents if you don’t trust your own validators.
• Better agents improve the environment. Better environment improves the agents. It compounds.
• And yes, the ceiling is not the model. The ceiling is your validation throughput.

So if the future you want is:
bug filed → agent picks it up → agent fixes it → tests pass → patch ships in under two hours…

Invest in the codebase that will be agent ready.
@FactoryAI at @aiDotEngineer AIE CODE