Most developers define themselves by their tech stack.
.NET dev. Azure architect. Full-stack engineer.
That’s not wrong. But it’s incomplete.
I use the phrase authority vector, because it helps position a developer where they currently are and point them toward where they’re going.
After sitting with it for a while, I landed on six data points:
- What I build
- Who I build it for
- What I build it with
- What I’m known for today
- My development philosophy
- Where I’m going
Knowing those six things, you can start to plot a path through your career.
What I like about this is that at any point any of them can move. You can change your tech stack. Start building different products. Change the direction you’re heading.
My working authority vector
What I build: High-performing, scalable solutions that solve complex problems simply.
Who I build it for: Enterprise teams and companies that need massive scalability and can’t afford downtime, whether starting fresh or fixing what’s broken.
What I build it with: .NET and Azure. APIs, Functions, Service Bus, distributed systems. SQL, Cosmos DB, and Elasticsearch for data. Uno Platform for front end.
What I’m known for today: Architecture and distributed systems at scale. The guy you call when the system is breaking under load, or needs to be built to handle it from the start.
My development philosophy:
- Use reusable patterns that make sense
- Don’t add complexity unless it earns its place
- Just because you can doesn’t mean you should
- Done is better than planned
- Graveyards are full of over-engineered projects
Where I’m going: Building AI-enabled solutions where personalization is standard, not a nice-to-have. Using the full stack to make intelligent, responsive experiences the baseline rather than the exception.
That’s mine. What’s yours?