01
Understand the problem first
I like to understand what the software actually needs to do before deciding how it should be built. The framework matters, but the problem comes first.
I'm Behon Baker.I build software &solve technical problems.
I'm a software developer with over a decade of experience across IT and software. Most of my work sits somewhere between frontend engineering, backend systems, databases, and the infrastructure needed to keep everything running.
I like being able to understand more than one layer of a product. I can work on the interface, trace a problem through an API, look at the data model, or figure out what's happening on the server. That perspective has shaped the way I build and maintain software.
How I got here
02
My path into software wasn't exactly a straight line.
- 01Quality Assurance
- 02IT & Systems
- 03Software Development
- 04Full-stack Engineering
- 05Technical Leadership & Architecture
My career started in quality assurance, where I spent a lot of time looking closely at how people used systems, finding problems, and helping teams improve the experience.
From there I moved into IT and systems administration, where I worked with servers, databases, internal systems, users, and the less glamorous parts of technology that still have to work every day.
Software development eventually became the natural next step. I moved into full-stack engineering, product development, technical leadership, and architecture, while keeping a lot of that earlier experience with me.
That background is probably why I rarely look at a feature as just a feature. I'm usually thinking about how it fits into the rest of the system, how it will be deployed, what data it depends on, how someone will maintain it, and what happens when something goes wrong.
How I work
03
The way I approach the work.
02
Keep the system understandable
I value code and architecture that another developer can reasonably pick up, understand, and maintain. Clever isn't always better.
03
Think beyond the frontend
A UI rarely exists by itself. I think about the API, data model, authentication, permissions, deployment, and infrastructure around it when those things affect the product.
04
Ship it, then support it
Getting something into production isn't the end of the work. I've spent years maintaining applications after launch, fixing issues, adding features, and learning from how people actually use them.
Tools & technology
04
Tools change. The fundamentals travel well.
I have tools I reach for often, but I don't think every project needs the same stack. These are the technologies I've spent the most time working with.
Frontend
- Nuxt
- Vue
- React
- Tailwind CSS
- Vuetify
Backend
- NestJS
- Express
- Django
- REST APIs
- GraphQL
Data
- PostgreSQL
- MySQL
- MongoDB
- Firebase
- Prisma
Systems & delivery
- Linux
- Docker
- Git
- Testing
- Deployment workflows
Open source & teaching
05
Some of the things I learn turn into things I share.
Some of what I build eventually becomes useful outside the original project.
UI Thing grew out of that mindset. It's a collection of Nuxt components and tooling built around the kinds of components I wanted to use in my own projects.
I also create coding content through Breezy Codes. Most of it comes from the same place: solving practical development problems, figuring out how something works, and then explaining it in a way another developer can use.
Outside software
06
I spend some time behind a camera too.
When I'm away from code, I've been spending more time learning photography. It scratches a different part of the same itch: paying attention to details, composition, light, and how individual pieces work together.
Currently
07
I'm open to interesting problems and good teams.
I'm open to full-time engineering roles, contract projects, consulting, ongoing development work, and technical collaborations. Most of my work is done remotely.
- Location
- Remote
- Timezone
- Pacific Time
- Working
- Primarily remote
- Contact
- Open to conversations
- Full-time engineering roles
- Contract work
- Freelance/product development
- Consulting
- Ongoing support
- Technical collaborations
Let's work together
Have something you think I'd be a good fit for?
Whether it's a role, a product, an existing system that needs some attention, or a technical problem you want another set of eyes on, feel free to reach out.