<?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: Nikos</title>
    <description>The latest articles on DEV Community by Nikos (@quantuminformation).</description>
    <link>https://dev.to/quantuminformation</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%2F245965%2Fd9d27fcf-56d1-4017-8ee6-d1a231abd120.jpeg</url>
      <title>DEV Community: Nikos</title>
      <link>https://dev.to/quantuminformation</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/quantuminformation"/>
    <language>en</language>
    <item>
      <title>What plastering my first wall taught me about software architecture</title>
      <dc:creator>Nikos</dc:creator>
      <pubDate>Fri, 10 Apr 2026 10:47:41 +0000</pubDate>
      <link>https://dev.to/quantuminformation/what-plastering-my-first-wall-taught-me-about-software-architecture-n76</link>
      <guid>https://dev.to/quantuminformation/what-plastering-my-first-wall-taught-me-about-software-architecture-n76</guid>
      <description>&lt;p&gt;&lt;strong&gt;Title&lt;/strong&gt;&lt;br&gt;
What plastering my first wall taught me about software architecture&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Body&lt;/strong&gt;&lt;br&gt;
Last week I plastered my first wall and made the mistake of doing it in halves.&lt;/p&gt;

&lt;p&gt;I finished the bottom section first, then moved up and did the top. The join between them turned messy because the wall should have been done in one continuous pass. I then spent the next 2 days fixing rough areas with jointing compound and sanding.&lt;/p&gt;

&lt;p&gt;What struck me was how architectural the mistake felt.&lt;/p&gt;

&lt;p&gt;The wall did not really fail in the flat middle. It failed at the join. That felt very close to software architecture, where problems often show up first at boundaries:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;between old and new code&lt;/li&gt;
&lt;li&gt;between services&lt;/li&gt;
&lt;li&gt;between frontend and backend&lt;/li&gt;
&lt;li&gt;between the model and the workflow it is supposed to support&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A few things stood out to me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The finish cannot rescue a weak layer underneath.&lt;/li&gt;
&lt;li&gt;Rework gets expensive fast once the next layer is already involved.&lt;/li&gt;
&lt;li&gt;Physical work gives immediate feedback. Software often delays it until integration or production.&lt;/li&gt;
&lt;li&gt;More effort is not always better effort if the sequencing is wrong.&lt;/li&gt;
&lt;li&gt;Cleanliness and discipline matter more than glamour.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point felt especially true architecturally. A lot of the work that keeps systems calm is not flashy: clear boundaries, clean environments, naming, predictable deployment, and not carrying old mistakes into the next layer.&lt;/p&gt;

&lt;p&gt;I wrote a longer version here if anyone is interested:&lt;br&gt;
&lt;a href="https://nikoskatsikanis.com/blog/plastering-code" rel="noopener noreferrer"&gt;https://nikoskatsikanis.com/blog/plastering-code&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Curious whether other people have found the same thing: architecture problems often stay hidden in the middle, but edges and joins tell the truth first.&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fiem8fysve5fm45dosiqj.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fiem8fysve5fm45dosiqj.JPG" alt=" " width="652" height="489"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>devjournal</category>
      <category>learning</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>Making redwoodjs videos!</title>
      <dc:creator>Nikos</dc:creator>
      <pubDate>Sat, 04 Jul 2020 21:09:22 +0000</pubDate>
      <link>https://dev.to/quantuminformation/making-reddwoodjs-videos-13k9</link>
      <guid>https://dev.to/quantuminformation/making-reddwoodjs-videos-13k9</guid>
      <description>&lt;p&gt;I'm not one for writing, but you can follow here!). :&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=v7-IwJ35xOE"&gt;https://www.youtube.com/watch?v=v7-IwJ35xOE&lt;/a&gt;&lt;/p&gt;

</description>
      <category>redwoodjs</category>
      <category>firebase</category>
      <category>svelte</category>
    </item>
    <item>
      <title>Fullstack starter for Svelte and netlify </title>
      <dc:creator>Nikos</dc:creator>
      <pubDate>Wed, 18 Dec 2019 22:13:18 +0000</pubDate>
      <link>https://dev.to/quantuminformation/fullstack-starter-for-svelte-and-netlify-1141</link>
      <guid>https://dev.to/quantuminformation/fullstack-starter-for-svelte-and-netlify-1141</guid>
      <description>&lt;p&gt;I made a fullstack starter for #svelte and netlify.&lt;/p&gt;

&lt;p&gt;live demo &lt;a href="https://svelte-netlify-identity.netlify.com"&gt;https://svelte-netlify-identity.netlify.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I will be adding support for firebase next.&lt;/p&gt;

&lt;p&gt;See the youtube series for full explanations.&lt;/p&gt;

&lt;p&gt;📘Svelte Fullstack Starter Playlist:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.youtube.com/playlist?list=PLCrwuqjmVebJeMDrAPQDrJmnwXWDw3CJW"&gt;https://www.youtube.com/playlist?list=PLCrwuqjmVebJeMDrAPQDrJmnwXWDw3CJW&lt;/a&gt;  &lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/QuantumInformation/svelte-fullstack-starter"&gt;https://github.com/QuantumInformation/svelte-fullstack-starter&lt;/a&gt;&lt;/p&gt;

</description>
      <category>svelte</category>
      <category>netlify</category>
      <category>firebase</category>
      <category>jamstack</category>
    </item>
    <item>
      <title>Svelte, Sapper and the Compiler step by step videos</title>
      <dc:creator>Nikos</dc:creator>
      <pubDate>Mon, 28 Oct 2019 08:34:05 +0000</pubDate>
      <link>https://dev.to/quantuminformation/svelte-and-the-compiler-step-by-step-videos-515k</link>
      <guid>https://dev.to/quantuminformation/svelte-and-the-compiler-step-by-step-videos-515k</guid>
      <description>&lt;p&gt;I'm making some in-depth videos on the Svelte compiler output. We will see how far I get:&lt;/p&gt;

&lt;p&gt;📘Svelte and Google Cloud masterclass playlist:&lt;br&gt;
&lt;a href="https://www.youtube.com/playlist?list=PLCrwuqjmVebK08Cwz_XB55cNKFfFYOMGo"&gt;https://www.youtube.com/playlist?list=PLCrwuqjmVebK08Cwz_XB55cNKFfFYOMGo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📘Svelte Compiler playlist:&lt;br&gt;
&lt;a href="https://www.youtube.com/watch?v=1LXEN0Pw6y0&amp;amp;list=PLCrwuqjmVebJoaVCVP5NOxEd4DLH6QUgK"&gt;https://www.youtube.com/watch?v=1LXEN0Pw6y0&amp;amp;list=PLCrwuqjmVebJoaVCVP5NOxEd4DLH6QUgK&lt;/a&gt;&lt;/p&gt;

</description>
      <category>svelte</category>
      <category>sapper</category>
      <category>googlecloud</category>
      <category>firebase</category>
    </item>
  </channel>
</rss>
