Practical over flashy
Solutions are shaped around real business processes, budgets, and timelines.
About me
I started programming in 2013 and have spent the years since building, maintaining, and improving software for real-world needs. In 2023 I began integrating AI into my development workflow — not to replace engineering judgment, but to work faster and explore solutions more thoroughly while keeping quality, security, and maintainability in my own hands.
My journey in software development began in 2013. Since then, I've focused on understanding problems before writing code — because the right solution depends on how a business actually works.
Over the years I've grown through hands-on development: writing and maintaining code, troubleshooting production issues, designing data models, and shaping software architecture that stays maintainable as requirements change.
Today I work as a freelance software developer, helping clients plan, build, and improve web applications, internal systems, integrations, and automations.
Professional timeline
2013
Began my journey in programming and software development.
2013–2022
Developed my skills in programming, troubleshooting, software architecture, and translating system requirements into working solutions.
2023
Started using AI to support coding, debugging, documentation, solution exploration, and overall workflow efficiency.
Present
Combining programming experience with AI technology to build digital solutions that are effective and maintainable.
Since 2023
Since 2023 I've used AI as a productivity tool across my workflow. It helps me move faster on repetitive work and explore more options — while every architectural decision, code review, security consideration, and final result remains my responsibility.
AI enhances my workflow — it doesn't replace programming fundamentals, software architecture, debugging, security awareness, or problem-solving. Every line that ships is reviewed and understood.
How I work
Solutions are shaped around real business processes, budgets, and timelines.
Clean structure, clear naming, and documentation so software can keep evolving.
Validation, access control, and safe data handling are part of the build, not an afterthought.
Clear scope, honest estimates, and regular progress updates throughout the project.
Start a project
Tell me about your project, your goals, or the problem you're trying to solve. I'll get back to you with practical next steps.
I usually respond within 1–2 business days.