This is the Leonidov Yevhen blog: notes from nineteen years of building software, written for people who have to ship something on Monday. I am a software architect and engineer, and I write here about the parts of the job that are hard to Google.
Who writes here
My name is Leonidov Yevhen. I have worked in IT since 2006: telecom hardware, Linux devices, traffic systems, a learning platform, an AI gateway and a WordPress security product. Today I lead GLOBUS.studio, a team of twenty-seven people in Ukraine, and I still write code because architecture without hands-on work turns into slides.
What I write about
- Web and mobile development, from the request path to the deploy.
- AI and machine learning, mostly the practical part: local models, RAG, orchestration.
- Cloud and infrastructure, with the bill attached.
- Cybersecurity and WordPress, where I have strong opinions and scars.
- Architecture and the daily craft of naming, testing and reading code.
What you will find in the Leonidov Yevhen blog
Practical material. A guide you can apply on Monday, not a summary of five other articles. Trade-offs stated as trade-offs: what a choice costs, when it stops working, what I would do differently. Numbers where I have them, and an honest “I do not know” where I do not.
How I write
One idea per article. Short paragraphs, concrete examples, code only where it explains something. I test the claims I can test, and I mark the rest as opinion. If an article ages badly, I would rather rewrite it than defend it.
Beyond code
Outside technology I paint, draw digital illustrations, follow motorsport and listen to a lot of music. These hobbies are not decoration: they train attention and taste, and both matter when you design an interface or debug a system at 2 a.m.
Comments and contact
Comments are open on every article. Ask a question, disagree, share a better solution. For private questions, use the contact page: email, Telegram or a call. I answer what I can, and I say so when I cannot help.
Three questions I get
Is the blog in English only? No. Every article exists in English, Russian and Ukrainian, and the translations are full versions, not summaries.
Do you accept guest posts? Rarely. If the material is specific and tested, write to me with an outline.
Can I republish an article? With a link to the original and no edits to the meaning, yes.
How this blog is built
WordPress, a custom theme, Polylang for three languages and Rank Math for SEO. No page builder, no tracking scripts beyond the analytics I need, no popups asking for an email before the first paragraph. The site is fast because it is small.
What I will not write
Hype about tools I have not used. Listicles with twenty items and no opinion. Text generated to fill a keyword. If an article has no tested claim, it does not go up.
Where to start
Open the archive and pick the topic you are fighting with today: security, architecture, SQL or the craft of code. Each article stands alone, and the related links at the bottom lead to the next one.
Thanks for reading. Start with the archive, pick a problem you have today, and see whether my notes save you an evening.
What you will not find in this blog
No news rewrites, no listicles, no filler. If a topic is here, I have done the work and paid for the mistake. WordPress news covers the announcements better than I ever will, and the Leonidov Yevhen blog stays a place for the notes that survived a real project.
Related reading: Beginner developer roadmap: where to start and The importance of correct naming in code.