<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design-Intent on Scholion</title><link>https://scholion.thluiz.com/tags/design-intent/</link><description>Recent content in Design-Intent on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/design-intent/index.xml" rel="self" type="application/rss+xml"/><item><title>Talk on expressing architecture in code: AgileRoots 2010</title><link>https://scholion.thluiz.com/notes/talk-on-expressing-architecture-in-code-agileroots-2010/</link><pubDate>Sun, 05 Jul 2020 14:10:33 +0000</pubDate><guid>https://scholion.thluiz.com/notes/talk-on-expressing-architecture-in-code-agileroots-2010/</guid><description>George Fairbanks says writing code that expresses design intent is hard but helpful, and this talk proposes architecturally evident coding patterns to make design and architecture easier to infer from code.</description></item></channel></rss>