How I grow as a Performance Engineer. From running load tests to thinking in systems. A roadmap that helps me connect tools, theory, and real impact.
Hi, I'm Vadzim Tuhuzbayeu 👋
A performance engineer sharing notes on performance.
I share the first stage of my open experiment with GetMeOne — designing the architecture and performance testing approach. Next up: metrics, JMeter, k6, analysis, and real-world optimizations. Just like on a real project.
Why interviews shouldn’t feel like exams. What really shows a person’s ability to think and how to tell apart an engineer who understands from one who just remembers.
Why NFRs aren't just bureaucracy but the foundation of every performance process. Here's how to define real performance criteria, who should set them, and what to do when a client says: "Just make it faster."
Each type of test answers its own question — where the limit is, what happens under a peak, and whether the system can run for days without crashing. In this article, I explain with real examples and graphs how I approach performance testing.
A story about how a single unclosed ExecutorService in Java caused native memory leaks and JVM crashes. And how it was fixed.
I’m not against AI. I’m for a thoughtful approach. In this article, I share why artificial intelligence is not a replacement for engineers, and how to build a process where AI actually adds value.
I share how I choose performance testing tools for different needs — from simple scenarios to complex distributed tests.
In this article I share my Miro performance testing map and walk through each step: from requirements to optimization, with practical tips from my experience.
A simple take on performance testing: why we need it, how it helps spot bottlenecks, figure out capacity, and make sure prod can handle the load.