<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Review on Justin Largo</title><link>https://justinlargo.com/tags/code-review/</link><description>Recent content in Code-Review on Justin Largo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 12 Sep 2026 13:00:00 -0400</lastBuildDate><atom:link href="https://justinlargo.com/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>The Junior's Guide to Agentic Engineering</title><link>https://justinlargo.com/posts/juniors-guide-to-agentic-engineering/</link><pubDate>Sat, 12 Sep 2026 13:00:00 -0400</pubDate><guid>https://justinlargo.com/posts/juniors-guide-to-agentic-engineering/</guid><description>&lt;p&gt;I&amp;rsquo;ve spent the last year getting handed projects that look like a hallucination in code form. I&amp;rsquo;ve written several posts about moving from hand-coding to agentic engineering; this is the practical one. It&amp;rsquo;s for new hires and for the non-technical folks building software with AI, and it exists because reviewing that kind of work has been causing me physical pain.&lt;/p&gt;&#10;&lt;p&gt;By agentic engineering I mean: you tell an AI agent what you want through software specifications (spec-driven development), it writes and runs the code, and you review the result instead of typing it yourself. That&amp;rsquo;s the opposite of vibe coding, where you prompt an agent to do things with no concrete criteria for what you want done.&lt;/p&gt;</description></item></channel></rss>