<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Writing on Home</title>
    <link>https://borisquiroz.dev/tags/writing/</link>
    <description>Recent content in Writing on Home</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>&lt;&lt; end &gt;&gt;</copyright>
    <lastBuildDate>Mon, 17 Feb 2025 05:58:12 -0300</lastBuildDate>
    <atom:link href="https://borisquiroz.dev/tags/writing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How writing helps in software architecture design</title>
      <link>https://borisquiroz.dev/posts/how-writing-helps-in-software-architecture-design/</link>
      <pubDate>Mon, 17 Feb 2025 05:58:12 -0300</pubDate>
      <guid>https://borisquiroz.dev/posts/how-writing-helps-in-software-architecture-design/</guid>
      <description>&lt;p&gt;In the fast-paced world of software engineering, it’s easy to feel pressured to&#xA;jump straight into coding when faced with a challenging problem. But sometimes,&#xA;taking a step back and slowing down can lead to surprising clarity. A few weeks&#xA;ago, I discovered the power of writing as a tool for software architecture&#xA;thinking, and I’d like to share how it helped me solve a problem that initially&#xA;seemed daunting.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
