Blazor

Why I Stopped Calling Myself a Web Developer

January 1, 2026

I've worked across Angular, Blazor, React, .NET, multiple architectures, and a dozen domains. Here's what that actually taught me — and why the label was the first thing to go.

Tags

#abp-framework (6) #mcp (5) #best-practices (4) #claude (4) #model-context-protocol (4) #.net (3) #asp.net-core (3) #clean-code (3) #cqrs (3) #ddd (3) #software-architecture (3) #ai (2) #ai-integration (2) #angular (2) #architecture (2) #authentication (2) #blazor (2) #clean-architecture (2) #domain-driven-design (2) #microservices (2) #modular-monolith (2) #oauth (2) #openiddict (2) #pkce (2) #software-engineering (2) #solid (2) #testing (2) #api-design (1) #backend (1) #bearer-token (1) #business-logic (1) #caching (1) #career-development (1) #claude-code (1) #code-quality (1) #code-review (1) #custom-pricing (1) #custom-theme (1) #debugging (1) #decorator-pattern (1) #dependency-injection (1) #design-patterns (1) #developer-workflow (1) #development-speed (1) #etag (1) #feature-management (1) #frontend (1) #http (1) #http-caching (1) #jwt (1) #layout (1) #leptonx (1) #middleware (1) #monolith (1) #multi-tenancy (1) #oop (1) #parallel-agents (1) #payments (1) #performance (1) #postgres (1) #postgresql (1) #productivity (1) #prorated-billing (1) #read-models (1) #redirect-uri (1) #refactoring (1) #regression-testing (1) #repository-pattern (1) #rest (1) #saas (1) #scrutor (1) #software-design (1) #subscription-system (1) #system-design (1) #tdd (1) #testability (1) #theme (1) #tools (1) #ui (1) #worktrees (1)