{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidmsbjaefkn3u2lhmixnmbtfaruh6rd2sa5w4ftgxd4g2wy2ooye4",
    "uri": "at://did:plc:orthdqmceconbkttbssisbxy/app.bsky.feed.post/3mgv37t3i5bb2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiecohrgtozrbpqci3qzwb7u4wethpc2nlmopdgal5bqhftqg7h4zu"
    },
    "mimeType": "image/jpeg",
    "size": 164528
  },
  "description": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n0:00\n\n/11:14\n\n\n1×\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBelow you'll find an AI transcription of everything we riffed about.\n\nKey distinction: Software Development vs. Software Engineering:\n\n * Software development (typing code, prompting LLMs) is accelerating massively and becoming ubiquitous—anyone (e.g., a hairdresser using Cursor) can now be a \"developer\" due to abundant AI knowledge/tools.\n   \n * Software engineering remains essential and is evolving: engineers now act like locomotive eng",
  "path": "/frontier/",
  "publishedAt": "2026-03-12T18:55:07.000Z",
  "site": "https://ghuntley.com",
  "tags": [
    "https://www.youtube.com/watch?v=SMVyUu-GTpU",
    "https://x.com/GeoffreyHuntley/status/2032163849067987280",
    "https://www.linkedin.com/posts/geoffreyhuntley_a-couple-of-days-ago-i-sat-down-with-vivek-activity-7437931906714791938-4_75"
  ],
  "textContent": "0:00\n\n/11:14\n\n1×\n\nBelow you'll find an AI transcription of everything we riffed about.\n\nKey distinction: Software Development vs. Software Engineering:\n\n  * Software development (typing code, prompting LLMs) is accelerating massively and becoming ubiquitous—anyone (e.g., a hairdresser using Cursor) can now be a \"developer\" due to abundant AI knowledge/tools.\n\n  * Software engineering remains essential and is evolving: engineers now act like locomotive engineers — keeping the \"train\" on tracks by designing safe, reliable systems/automations rather than working \"in\" the business (manual coding).\n\n  * Shift focus to designing loops, automations, safety mechanisms (e.g., sandboxing, credential management, security), risk engineering, and responsible AI utilization.\n\n\n\n## Implications for professionals:\n\n  * If your identity is tied to being a traditional \"software developer\" (keyboard typing), it's a tough time—prompting for outcomes is the new norm.\n  * If your employer bans AI tools, leave immediately: it's business suicide to ignore AI, while staying risks employability suicide as the market for manual coders shrinks rapidly.\n  * Engineers should prioritize raw technical/cognitive skills → engineer away concerns (e.g., replace binary code reviews with risk-based approaches, feature flags, constrained blast radius, auto-migrations).\n\n\n\n\n## Open source is \"dead\" (or greatly diminished):\n\n  * Traditional open-source libraries existed to ease hiring and sharing reusable code.\n  * Now, with AI generation, there's little point: generating code avoids maintainer burnout, GitHub issue delays, abandoned projects, supply-chain attacks (e.g., npm takeovers), and Dependabot update toil.\n  * Better to generate first-party code for faster evolution, full control, and no human \"tool calls\" (which disqualifies true AGI-like autonomy).\n  * Exceptions: highly sensitive areas like PKI/SSL where generation isn't appropriate.\n\n\n\n## Broader industry shifts in an abundance era:\n\n\n  * Software moves from scarcity (differentiated libraries, hard-to-replicate tech) to abundance (easy generation/reimplementation).\n\n  * Many software products become hyper-commodity (like utilities: electricity, web hosting) — easily screenshot + reimplemented via AI (e.g., Claude).\n\n\n\n### Vendor lock-in and switching costs vanish (e.g., auto-migrating databases/apps).\n\n  * True moats now lie in non-technical areas: contracts, relationships, handshakes, stakes, distribution, taste/judgment — the \"hard things of business.\"\n  * Unit economics of software have fundamentally changed → questions if software remains investable (VCs unsure about moats, fundraising challenges).\n\n\n\n\n> Future: hyper-personalized software; old models of building/scaling via scarcity are disrupted.\n\n### Closing advice\n\n  * Stay relevant by running fast, staying curious, and adapting to the \"brave new world.\"\n\n\n\nps. this interview is also available:\n\n  * on youtube at https://www.youtube.com/watch?v=SMVyUu-GTpU\n  * X - https://x.com/GeoffreyHuntley/status/2032163849067987280\n  * LinkedIn - https://www.linkedin.com/posts/geoffreyhuntley_a-couple-of-days-ago-i-sat-down-with-vivek-activity-7437931906714791938-4_75\n\n",
  "title": "A couple of days ago, I sat down with Vivek Bharathi and dumped my brains. Here's the interview...",
  "updatedAt": "2026-03-12T18:56:09.403Z"
}