<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>GoogleIO on Vasileios Chroniadis blog</title><link>https://chronvas.github.io/tags/googleio/</link><description>Recent content in GoogleIO on Vasileios Chroniadis blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chronvas.github.io/tags/googleio/index.xml" rel="self" type="application/rss+xml"/><item><title>The Socio-Technical Crossroads - Engineering in an Era of Infinite Output</title><link>https://chronvas.github.io/posts/2026-05-19-the-socio-technical-crossroads--engineering-in-an-era-of-infinite-output/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://chronvas.github.io/posts/2026-05-19-the-socio-technical-crossroads--engineering-in-an-era-of-infinite-output/</guid><description>&lt;p&gt;Today I watched an incredible Google I/O presentation by Adam Bender titled &amp;ldquo;Software Engineering at the Tipping Point.&amp;rdquo; It perfectly articulated something I’ve been thinking about a lot: as AI automates the &amp;ldquo;how&amp;rdquo; of writing code, our jobs are rapidly shifting toward the &amp;ldquo;why.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;For decades, as software engineers, we have poured our values, our ethos, and our intentions into products through our code. We used our techne—our technical craft—to express what we valued. We valued mastery over specific languages like Kotlin or framework architectures.&lt;/p&gt;</description></item></channel></rss>