<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering-Organization on Scholion</title><link>https://scholion.thluiz.com/tags/engineering-organization/</link><description>Recent content in Engineering-Organization on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Wed, 23 Sep 2026 20:10:34 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/engineering-organization/index.xml" rel="self" type="application/rss+xml"/><item><title>Micro And Macro Software Architectures, Why You Need Both</title><link>https://scholion.thluiz.com/notes/micro-and-macro-software-architectures/</link><pubDate>Wed, 23 Sep 2026 19:08:24 +0100</pubDate><guid>https://scholion.thluiz.com/notes/micro-and-macro-software-architectures/</guid><description>Draws the line between macro architecture decisions a company makes once for everyone and micro architecture decisions each team makes for itself, and argues both need to be explicit.</description></item></channel></rss>