Blog posts like this have noble intentions but since they often lack real world examples and actual code, I don't find them very useful. Everyone has a differen

Blog posts like this have noble intentions but since they often lack real world examples and actual code, I don't find them very useful. Everyone has a different interpretation of what constitutes dumb or simple code. In fact, the absence of concrete, unambiguous, actionable advice is something I always found fascinating about software engineering. My background is in medicine where it's much more common to follow flow charts, go through check lists and administer first line treatment that's based on empirical evidence. I understand that this is very hard to implement in software, but the almost complete absence of it means that every project is more or less unique. Sure, if you zoom out far enough then a lot of back ends boil down to "get data from DB apply to template" but it can still be surprisingly challenging to take your knowledge from one such system and apply them to the next.