<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microservices on</title><link>https://eunus.dev/tags/microservices/</link><description>Recent content in Microservices on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 01 Jan 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Stopped Calling Myself a Web Developer</title><link>https://eunus.dev/blog/why-i-stopped-calling-myself-a-web-developer/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/why-i-stopped-calling-myself-a-web-developer/</guid><description>When someone asks me what I do, I used to say &amp;ldquo;I&amp;rsquo;m a web developer.&amp;rdquo; It felt accurate. I built web apps. I wrote APIs. I worked with databases.
But somewhere between my first monolith and my fourth SaaS system, that label stopped feeling right. I wasn&amp;rsquo;t just building web pages anymore. I was making decisions about how systems would grow over five years, how teams would own code without stepping on each other, and why a system that looked fine at 100 users started falling apart at 10,000.</description></item></channel></rss>