<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coding Best Practices on blog.pierrehenry.be</title><link>https://blog.pierrehenry.be/tags/coding-best-practices/</link><description>Recent content in Coding Best Practices on blog.pierrehenry.be</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Pierre-Henry Soria.</copyright><lastBuildDate>Tue, 30 Dec 2025 15:32:58 +0000</lastBuildDate><atom:link href="https://blog.pierrehenry.be/tags/coding-best-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>Adopt Big Picture Thinking or Write Messy Code Forever</title><link>https://blog.pierrehenry.be/blog/adopt-big-picture-thinking-or-write-messy-code-forever/</link><pubDate>Tue, 30 Dec 2025 15:32:58 +0000</pubDate><guid>https://blog.pierrehenry.be/blog/adopt-big-picture-thinking-or-write-messy-code-forever/</guid><description>You know, as a software engineer, it’s so tempting to just dive right into the code. I get it. There’s this urge to open up your editor, start hammering away, maybe even fire up some AI tool to spi&amp;hellip;</description></item></channel></rss>