<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Full Stack on</title><link>https://eunus.dev/tags/full-stack/</link><description>Recent content in Full Stack on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Thu, 01 Jan 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/full-stack/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>Early in my career, I would have described myself as a .NET developer. Then a project came along that needed Blazor. Then another needed React. Then Next.js, then MAUI, then Angular, then ABP Framework.
I didn&amp;rsquo;t plan to work across all of them. It just happened — one project at a time. And somewhere along the way I stopped thinking of myself as an Angular developer, or a Blazor developer, or any kind of framework developer.</description></item></channel></rss>