Solution Before Technology
I do not start with technology. I start with the problem.
Before choosing a tool, a platform, or a vendor, I want to understand what actually needs to be solved. That applies to software, infrastructure, and technical systems in general. In some cases, the right answer may be a server setup or a web application. In others, it may be a practical decision about hardware, interfaces, or workflow.
For me, good technical work begins with careful analysis. Once the problem is clear, the right solution usually becomes easier to identify.
Free Software for Free People
Whenever possible, I prefer Free and Open Source Software. This is not just a technical preference, but also a personal one.
“Free Software for free People” expresses something I strongly believe in: transparency, independence, and the freedom to understand, adapt, and maintain the tools we rely on. Open-source solutions also benefit from broader review and often provide a very solid foundation for long-term use.
That said, I am not dogmatic. If a closed-source solution is clearly the better fit for a specific requirement, I will use it. What matters most is choosing responsibly and with a clear understanding of the trade-offs. Costs exist either way, so the real question is whether a solution is sustainable, maintainable, and appropriate for the task.
Plan, Build, Test, Reevaluate
My work usually follows a simple cycle: first understand, then plan, then build, test, and reevaluate.
I often begin with notes, then move to sketches or diagrams to make the structure visible. From there, implementation starts, followed by testing and a careful review of what works, what does not, and what can be improved.
I do not see this as a rigid process, but as a practical cycle that repeats until the result is good enough to be useful, reliable, and maintainable. In my experience, strong solutions rarely appear all at once. They evolve through iteration.
Good Work Includes the Right People
I do not believe that professionalism means doing everything yourself.
One of the most important things I have learned over time is knowing when someone else has deeper expertise in a specific area. If another professional can solve part of a problem faster, better, and more economically, then involving that person is not a weakness — it is simply good judgment.
Good work includes the right people. That means listening to specialists, understanding different perspectives, and making sure the people with the right knowledge are part of the process. In the end, collaboration usually leads to better results than unnecessary self-reliance.
Practical, Not Trend-Driven
I am interested in new technologies, but I try not to follow trends for their own sake.
What matters to me is whether something is genuinely useful in practice. A new tool, platform, or idea should solve a real problem, improve a workflow, or make a system easier to understand and maintain. If it does not, then being new is not enough.
I value solutions that are clear, dependable, and realistic. In the long run, practicality matters more than hype.