<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on Mohseen</title><link>https://www.mohseen.dev/tags/engineering/</link><description>Recent content in Engineering on Mohseen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Dec 2021 12:28:42 -0800</lastBuildDate><atom:link href="https://www.mohseen.dev/tags/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>7 Reasons Config as Source of Truth is better than Code</title><link>https://www.mohseen.dev/post/2021-12-22-7-reasons-config-as-source-of-truth-is-better-than-code/</link><pubDate>Wed, 22 Dec 2021 12:28:42 -0800</pubDate><guid>https://www.mohseen.dev/post/2021-12-22-7-reasons-config-as-source-of-truth-is-better-than-code/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Heya Folks, wanted to share a few thoughts on which is better code or config for defining features in web apps or in general any application.
While it seems like a minor detail, but I strongly feel it affects how well someone can use or extend an application. For that reason, I wanted to share about 7 reasons why you should consider building features using config vs baked in code.&lt;/p&gt;</description></item></channel></rss>