<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Principal-Engineer on coles.codes</title><link>https://coles.codes/tags/principal-engineer/</link><description>Recent content in Principal-Engineer on coles.codes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://coles.codes/tags/principal-engineer/index.xml" rel="self" type="application/rss+xml"/><item><title>The shapeshifting engineer</title><link>https://coles.codes/posts/the-shapeshifting-engineer/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://coles.codes/posts/the-shapeshifting-engineer/</guid><description>&lt;p>This post is for the mids, seniors, and principals trying to work out what our jobs look like now that the machine writes the code. If you&amp;rsquo;re early in your career and wondering whether the whole thing is still worth pursuing, that&amp;rsquo;s a different conversation and I&amp;rsquo;ll write it up separately soon.&lt;/p>
&lt;p>I&amp;rsquo;ve been building software for over a decade, and these days I use AI coding tools every working day. The velocity is genuinely something. I&amp;rsquo;ve shipped features in an afternoon that would have taken me most of a week, and cleared backlog items that sat untouched for a year because the effort never justified the payoff.&lt;/p></description></item></channel></rss>