<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Productivity on</title><link>https://raze.mx/tags/productivity/</link><description>Recent content in Productivity on</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 21 Sep 2025 09:00:00 -0500</lastBuildDate><atom:link href="https://raze.mx/tags/productivity/index.xml" rel="self" type="application/rss+xml"/><item><title>Riding the Rails with GitHub Copilot: A Journey from Code Conductor to Passenger</title><link>https://raze.mx/post/github-copilot/</link><pubDate>Sun, 21 Sep 2025 09:00:00 -0500</pubDate><guid>https://raze.mx/post/github-copilot/</guid><description>&lt;h2 id="all-aboard-the-ai-express"&gt;All Aboard the AI Express&lt;/h2&gt;
&lt;p&gt;Picture this: You&amp;rsquo;re standing on a train platform, staring at a massive, rusted locomotive that&amp;rsquo;s been sitting idle for years. The engine is your legacy codebase—full of promise but plagued with mysterious errors, outdated dependencies, and that one function everyone&amp;rsquo;s afraid to touch because &amp;ldquo;it just works.&amp;rdquo; Then GitHub Copilot walks up, tips its conductor&amp;rsquo;s hat, and says, &amp;ldquo;Mind if I take the wheel?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s exactly how my journey with GitHub Copilot began six months ago. What started as curiosity about AI-assisted coding has evolved into a fundamental shift in how I approach software development. But here&amp;rsquo;s the thing—watching Copilot work is like being a passenger on a high-speed train, observing the landscape blur by while occasionally wondering, &amp;ldquo;How does it know to take that exact route?&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>