<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering on christos gkoros</title>
    <link>https://christosgkoros.com/tags/engineering/</link>
    <description>Recent content in Engineering on christos gkoros</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 28 May 2026 08:00:00 +0300</lastBuildDate>
    <atom:link href="https://christosgkoros.com/tags/engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A waterfall dream</title>
      <link>https://christosgkoros.com/posts/2026/05/28/a-waterfall-dream/</link>
      <pubDate>Thu, 28 May 2026 08:00:00 +0300</pubDate>
      <guid>https://christosgkoros.com/posts/2026/05/28/a-waterfall-dream/</guid>
      <description>The shape is contracting Product engineering got complicated for good reasons. Product managers to translate intent. Designers to translate experience. Engineers to translate constraints. Each role existed to own a part of the feedback loop process because no one person could hold all at once. At least not at scale.&#xA;That is the assumption AI is dissolving. The translation layers between roles were never the work — they were the cost of distributing it across people.</description>
    </item>
  </channel>
</rss>
