<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remote-Work on eval ( code )</title><link>https://evalcode.com/tags/remote-work/</link><description>Recent content in Remote-Work on eval ( code )</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copy, _right?_ :thinking_face:. All thoughts and opinions are my own. They do not represent my employer.</copyright><lastBuildDate>Tue, 03 Mar 2026 15:00:00 +0000</lastBuildDate><atom:link href="https://evalcode.com/tags/remote-work/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Exposed the Process Debt You've Been Ignoring</title><link>https://evalcode.com/posts/ai-exposed-your-process-debt/</link><pubDate>Tue, 03 Mar 2026 15:00:00 +0000</pubDate><guid>https://evalcode.com/posts/ai-exposed-your-process-debt/</guid><description>AI made code cheap. The bottleneck was never the code. It was scoping, estimation, and communication, the skills teams treated as optional for years. That bet no longer pays off.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://evalcode.com/posts/ai-exposed-your-process-debt/featured.jpg"/></item><item><title>Going Remote</title><link>https://evalcode.com/posts/going-remote/</link><pubDate>Fri, 01 Mar 2019 22:14:31 +0000</pubDate><guid>https://evalcode.com/posts/going-remote/</guid><description>The habits that made you successful in an office will hurt you when you go remote. Here&amp;rsquo;s how to replace observational communication with written communication.</description></item></channel></rss>