<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development Best Practices on blog.pierrehenry.be</title><link>https://blog.pierrehenry.be/tags/development-best-practices/</link><description>Recent content in Development Best Practices on blog.pierrehenry.be</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright © 2026, Pierre-Henry Soria.</copyright><lastBuildDate>Sun, 14 Dec 2025 00:46:10 +0000</lastBuildDate><atom:link href="https://blog.pierrehenry.be/tags/development-best-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>Use Feature Toggles or Stay Stuck as an Average Developer</title><link>https://blog.pierrehenry.be/blog/use-feature-toggles-or-stay-stuck-as-an-average-developer/</link><pubDate>Sun, 14 Dec 2025 00:46:10 +0000</pubDate><guid>https://blog.pierrehenry.be/blog/use-feature-toggles-or-stay-stuck-as-an-average-developer/</guid><description>Let’s talk about something that gets overlooked way too often: how you ship features and handle mistakes in production. I see a lot of teams just rolling with the default, average approach—deploy,&amp;hellip;</description></item></channel></rss>