<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design Patterns on</title><link>https://eunus.dev/tags/design-patterns/</link><description>Recent content in Design Patterns on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/design-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>What Working With a Greek Engineer Taught Me</title><link>https://eunus.dev/blog/what-working-with-a-greek-engineer-taught-me/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/what-working-with-a-greek-engineer-taught-me/</guid><description>Some lessons arrive through documentation. Others arrive through a disagreement on a real system, under real pressure — and you don&amp;rsquo;t fully understand what you learned until months later.
I spent several months working on a Hospital Management System built on ABP Framework with Blazor. The lead engineer on the client side reviewed everything, had strong opinions about most of it, and was not the kind of person who accepted &amp;ldquo;it works&amp;rdquo; as a sufficient answer.</description></item></channel></rss>