Skills

I have been programming for over a decade, primarily in web technologies—most frequently within the PHP ecosystem using frameworks like Yii, Zend, and Symfony. I typically worked as a full-stack developer with a strong backend leaning.

In recent years, I have expanded my experience to include ReactJS and Node, often using them alongside PHP in a hybrid setup to implement microservices or proxy layers. React is my go-to choice for building dynamic, real-time user interfaces, where optimization and lightweight design are crucial.

I prioritize application performance and security; nowadays, ANYONE can easily build an application using AI vibe-coding that runs smoothly and fulfills its function. Over the past few months, I have experimented with this approach myself, and it yields phenomenal results, especially when learning new technologies. However, there is an important caveat—AI operates based on prompts that someone has to devise in accordance with the general concept of the system.

Expand

You can create dozens of features in a flash, but in the end, they more or less need to be integrated—usually regarding security and performance.

A person without technical knowledge can perfectly describe the business requirements of an application and make it work. But they will not always account for data security, solution portability (Linux / Windows), or performance optimization.

I have noticed on numerous occasions that you need to make AI aware of certain things—sure, I use Windows and it works on my machine, but for instance, I realize that paths, files, and permission systems differ between Linux and Windows, and I can foresee beforehand that it won't work on a Debian server or that there will be a security vulnerability.

I generally write code myself—sometimes I ask AI to generate snippets, but I study them thoroughly and modify them to suit my needs. Most often, I commission it for code reviews, consult architectural design questions, and ask about commonly used standards and current technologies.

I develop cross-platform—I use both Windows and Linux, and for larger projects, I run the environment in Docker to ensure full compatibility. I use Git for version control, and for CI/CD solutions, I have used Jenkins, AWS, and Azure. For private and solo projects, I make a habit of writing simple deployment scripts in NodeJS, where the entire build is executed on my machine, and the built project (stripped of development files) is uploaded via FTP script to the target share, which is much safer and usually faster.

In the early days of computing, programmers wrote optimized code with very few tools at hand and severely limited hardware resources. The modern trend is quite the opposite—dozens or hundreds of dependencies in projects; instead of optimizing legacy code, companies often resort to buying more cloud computing power. I have worked on several very large projects, and that is how it operated there, especially since no one wanted to touch legacy code (rightfully so) out of fear of breaking it. Based on what I have seen, I try to minimize dependencies and sometimes abandon libraries that are trendy but not always business-justified.

This website is built with FlightPHP, one of the lightest and fastest frameworks. I could have just as well written it in plain PHP, which I considered, but that would be going too far in the other direction; the framework provides me primarily with routing, a few patterns like Service Locator, and request handling. In FlightPHP, using Latte for rendering views is recommended, but I opted out of that element—I render views based on Markdown, which is the easiest to translate. Ultimately, I will probably generate all subpages as static .html files and deploy them to the server in that form, with styles and some scripts minified directly into the page code (on weak hosting this improves performance, on good hosting it degrades it), which will allow loading times to drop below the 350ms average; this might be art for art's sake, but I want to test how much it impacts performance, which will come in handy in other projects.

I dropped the idea of using React—which I really like and would prefer to use everywhere possible—nevertheless, vanilla React is not great for SEO and introduces a number of limitations. Instead, I used the Alpine.js library, which I learned about from Gemini, and it is completely sufficient for the simple logic I needed to implement here. Why do I need a mass of unnecessary dependencies when the goal is clear: to create a simple, readable website that loads in a fraction of a second and is SEO-friendly. I could use WordPress; it might be a bit simpler, but the site would already take several seconds to load and would be vulnerable to attacks—to achieve similar security and performance, I would ultimately have to spend more time. WordPress itself is secure, but the plugins and themes I might potentially use are not necessarily so.

DEV