<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Daniel</title>
    <description>The latest articles on DEV Community by Daniel (@salzaverde).</description>
    <link>https://dev.to/salzaverde</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3814643%2Fb957f687-fb9a-45d1-8317-d6a1a912b7cc.png</url>
      <title>DEV Community: Daniel</title>
      <link>https://dev.to/salzaverde</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/salzaverde"/>
    <language>en</language>
    <item>
      <title>Early POC: Documenting Software architecture with C4 and the Structurizr DSL</title>
      <dc:creator>Daniel</dc:creator>
      <pubDate>Tue, 14 Apr 2026 15:37:50 +0000</pubDate>
      <link>https://dev.to/salzaverde/early-poc-documenting-software-architecture-with-c4-and-the-structurizr-dsl-1e3i</link>
      <guid>https://dev.to/salzaverde/early-poc-documenting-software-architecture-with-c4-and-the-structurizr-dsl-1e3i</guid>
      <description>&lt;p&gt;A couple of months ago I conducted a public ODI/Jobs-to-be-done research on current pain points of documenting software architecture.&lt;/p&gt;

&lt;p&gt;I'm excited to share a very early proof of concept of the derived solution at &lt;a href="https://app.maniok.io" rel="noopener noreferrer"&gt;https://app.maniok.io&lt;/a&gt;&lt;br&gt;
It currently only works for public repositories and is &lt;a href="https://github.com/danischuetz/maniok" rel="noopener noreferrer"&gt;open source&lt;/a&gt; (MIT licensed)&lt;/p&gt;

&lt;p&gt;In essence, it is a Structurizr / C4 diagrams renderer that works on git repositories containing Structurizr documentation.&lt;/p&gt;

&lt;p&gt;Support for Structurizr is very basic and there are a couple of known issues (listed in the docs).&lt;/p&gt;

&lt;p&gt;What do you think?&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>sideprojects</category>
      <category>software</category>
    </item>
    <item>
      <title>Building a better tool for documenting software architecture</title>
      <dc:creator>Daniel</dc:creator>
      <pubDate>Mon, 09 Mar 2026 14:58:05 +0000</pubDate>
      <link>https://dev.to/salzaverde/building-a-better-tool-for-documenting-software-architecture-4hd4</link>
      <guid>https://dev.to/salzaverde/building-a-better-tool-for-documenting-software-architecture-4hd4</guid>
      <description>&lt;p&gt;Having spent extensive time researching options to document software architecture, not finding a satisfying solution to serve my needs, I’ve decided to build something that does.&lt;/p&gt;

&lt;p&gt;I want to make it worth the effort by founding this project on solid data, using the jobs-to-be-done framework and outcome driven innovation (ODI) to identify underserved needs in the segment. &lt;/p&gt;

&lt;p&gt;Based on the desired outcomes analysis I've created this survey: &lt;a href="https://forms.gle/2dtEAad6xirS4Ejy5" rel="noopener noreferrer"&gt;https://forms.gle/2dtEAad6xirS4Ejy5&lt;/a&gt; (it takes about 15 minutes to complete)&lt;/p&gt;

&lt;p&gt;The aggregated results will be shared publicly and participants can optionally gain early access to the tooling developed on conclusion of the survey.&lt;/p&gt;

&lt;p&gt;Would greatly appreciate your input and am looking forward to your thoughts on the project!&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>documentation</category>
    </item>
  </channel>
</rss>
