trying_to_be_an_engineer
I build web applications, backend systems, and explore server infrastructure. I've worked on complex applications, production APIs, and server environments. This is where I continue learning engineering by building tools and systems that solve real problems.
About
I'm Uzair, a web developer, backend engineer, and system administrator. I've built and maintained web applications, production backend systems, and server infrastructure using Laravel, Python, and various other tools.
My work spans the full stack of backend development—designing APIs, managing databases, building server environments, handling deployments, and ensuring systems run reliably under real load. I've also worked extensively with WordPress and Shopify when those platforms are the right fit for the problem.
I help others build reliable systems. Good engineering isn't about using the newest framework or the most complex architecture—it's about choosing the right level of complexity for the problem. Sometimes that's a custom application. Sometimes it's a well-configured platform. Sometimes it's a simple script.
This site documents the tools, experiments, and systems I build while continuing to deepen my engineering understanding. If you're working on something where thoughtful backend work and systems thinking matter, let's talk.
What I Work On
Web applications, backend services, and infrastructure.
I build complete web applications—frontend and backend working together. This includes designing APIs, structuring databases, implementing authentication and authorization, handling file uploads, managing background jobs, and ensuring everything deploys reliably.
On the infrastructure side, I work with Linux servers, deployment pipelines, environment configuration, monitoring, and the operational concerns that keep systems running. I've managed production environments, debugged performance issues, and built automation to reduce manual work.
How I Approach Engineering
Reliability over flash
I focus on building systems that work consistently. Handling edge cases, preventing bugs, and making sure features behave as expected are priorities in my daily work.
Maintainability over cleverness
Code is read more than it's written. I strive for clear, organized code that is easy for me or others to revisit and modify later.
Right tool for the job
I try to match the solution to the problem. Sometimes a simple script works; sometimes a small web service is better. Choosing the right approach saves time and reduces complexity.
Learning by doing
I learn most from actually building and fixing things. Debugging, testing, and iterating teach lessons you can’t get from tutorials alone.
Tools when needed
When I face repetitive problems, I automate or create small tools to make the workflow smoother. Tools grow naturally from repeated challenges, not hypothetical scenarios.
Build With Me
Follow along as I build tools, systems, and applications in public. I share what I'm working on, technical decisions from real projects, and lessons from production systems.
No marketing copy. No growth hacks. Just engineering work, documented as it happens.
Propose a Problem
What repetitive tasks waste your time? What workflows are broken? What systems don't scale the way they should?
Describing real problems helps me understand what's worth building next. Your input might lead to a tool, an article, or a custom solution. Either way, it shapes the work that happens here.