@nicbstme It's also gotten easier to duct tape + glue with AI, no vibe coding needed, like for eg., I use Grokbot + Notion as our ATS, not scalable long term, and plan on buying once we reach scale
all of my imessages & email now run through a single agent interface.
i still text, but i deleted every email client from my phone & canceled every email subscription or app i had.
gmail is basically just a database to me now. increasingly so are the rest of google’s services. i.e. i never want to manually write an email, create a doc, build slides, organize a calendar, or manage files again. i just want to express intent & have the underlying systems of record updated correctly. i think now you’ll see apps disappear quickly. many will become databases at best or entirely obsolete at worst.
the agent will be the default interface to your personal & professional life.
@armenberjikly behind the scenes browser use was killer, felt like it could do everything a human cloud which unlocks boring admin stuff. grok bot also does it but ux felt clunky.
tried them all - chatgpt, claude, perplexity, grok, poke.
spent this weekend with instinct and knocked out more personal admin than i have in months. got my wife on it too and it's the first one she's truly loved and actually uses.
haven't felt this magic since chatgpt.
Anyone that works in AI is working the hardest they've ever worked in their lives. On the surface it's somewhat ironic (AI should give us back time!), but the reality is that it's the most fun, fascinating and empowering epoch in human history. The intelligence revolution.
Building software by prompting agents without ever reading or editing the code directly isn't actually a new thing. It's just called being an engineering *manager*. We have decades of experience about how to be effective as engineering managers. It is a different skill, though.
One pattern I find useful for working with LLMs is a nice long ramble session. Sometimes the LLM needs more bits to understand what you're trying to achieve, but you're too lazy to type them. In these cases I like to lean back, switch to /voice and just ramble for like 10 minutes, total mess, anything goes, full stream of consciousness. Sometimes I declare it up top, something like "switching to speech recognition sorry for any typos...". Sometimes I turn it into a small interview of a few turns. But I find that the LLMs are somehow very good at reconstructing long incoherent rambles and often their echo of your own tangle of thoughts comes out quite a bit cleaner than what you started with. The result is that you improve the mind meld and have to correct things less from that point on.
We have been thinking about this a lot at @cora_ai.
We're building this for customer success first because that's where longitudinal account context matters a lot.
But the principle extends to the whole company. To be AI native, organizations will require the right data architecture, and that's exactly what we are building.
Increasingly, I believe companies may need to be rebuilt from the ground up, where you have a single timeline of all observability + product metrics + file changes laid out in a retrievable system, like Datadog + Posthog + Google Drive + Slack (really unified filesystem of Claude Code chats + Codex chats). This might be the new data foundation for any and all companies to maximize AI. Needs to be rebuilt because keeping track of diffs on existing system basically impossible to produce longitudinal information on decisions and rollbacks, something coding agent storage companies are actively trying to figure out, but this should extend to businesses as a whole.
Highly skeptical existing businesses will adopt this though because it means overhauling everything about their instrumentation and business data, but I think businesses built on this foundation probably can execute 100x better and faster
Q: How are job postings for software engineers rising rapidly despite AI agents automating coding?
A: Because there’s far more code to manage than ever before. We’re already seeing a 14x YoY increase in GitHub commits, and it’s accelerating.
AI has dramatically lowered the cost of writing code, so it’s now being used across far more businesses, applications, and use cases.
We’re at the beginning of a massive productivity boom driven by the proliferation of bespoke software throughout the entire economy.
Coding has been AI’s breakout use case this year. The fact that it’s increased demand for software engineers — rather than decreased it — should call into question the entire “AI will cause mass job loss” narrative.
Fully agree.
The moment the agent starts writing an HTML email template, though, all the formatting benefits collapse, most email clients strip the CSS, and you're back to debugging email client quirks. Markdown (with controlled HTML post processing) or plain text still wins there.
POD-OF-ONE: THE NEW ORG BUILDING BLOCK
As a @coinbase board member, t’s been a privilege to watch @brian_armstrong@emiliemc, and the Coinbase team build a true AI-native company.
Brian's whole post is worth reading in depth. I want to focus in on one thing that Coinbase is testing: “one-person product teams.”
Most of the AI discourse has focused on one-person companies. The more powerful and more broadly applicable construct will likely be one-person teams inside companies.
The old product org split context across 3 people. The designer held the user experience. The PM held the customer and prioritization context. The engineer held the code and systems context. Coordination was the price you paid to combine those views into one shipping decision.
Agents reduce that coordination cost.
A single high-agency person can now ask agents to draft flows, write code, run QA, summarize customer feedback, generate variants, check edge cases, and produce release notes.
This model rewards a very specific kind of builder:
• Technical enough to inspect the work
• Product-minded enough to choose the right problem
• Tasteful enough to reject mediocre output
• Fast enough to ship before the org forms around the idea
The scarce skill is judgment.
One strong person with customer context and good taste can now do the work of a small pod. One weak person with agents just creates more output for someone else to review.
This changes how early-stage founders should hire.
The most useful hiring question is now: “Can this person own the outcome end-to-end?”
That’s a higher bar than a functional job description. It blends product sense, technical range, design taste, writing clarity, and operating discipline. The title matters less. The span matters more.
Call it pod-of-one thinking.
A pod-of-one builder can go from ambiguous customer pain to shipped v1 without waiting for specs, mocks, tickets, handoffs, or meetings. Agents fill in missing labor. The human carries the context.
Teams still matter. They should form when the surface area is real: multiple customer segments, production risk, complex GTM loops, or enough product depth that specialization pays for itself.
Before that, a pod-of-one may be the fastest shipping unit in the company.
Founders: hire people who can be pods-of-one, who can carry the whole problem in their head and use agents to increase their throughput.