Most engineers eventually face the need to perform load testing: validating how a service scales, testing a new database, or running performance benchmarks for a new technology. At that point the obvious question arises — which tool should you use? Existing solutions work well for HTTP load testing, but they often become limiting when you need to test other protocols, model complex workload patterns (open vs closed systems, skewed distributions, hot partitions), or run distributed load testing in a cluster. In this talk, I will introduce NBomber — a load testing framework I created to address these challenges. We will cover: - why there was a need to build a new tool despite the existence of Gatling, Locust, and k6 - using .NET and F# to build latency-sensitive systems - the architecture of NBomber - how NBomber Cluster works - several practical use cases including database benchmarks, anomaly detection, Kubernetes integration, benchmark comparison, and performance trend analysis.

In the age of AI, anyone can generate code — even your team lead or the baker next door. But who ensures its quality? This talk will show why TDD is more relevant than ever, how to tell a good test from a bad one, make AI write proper code from the start, and why discipline and architectural thinking save both your nerves and your projects.

In this talk, I'll share my experience as a testing consultant and why testing is the responsibility of the whole team. We'll cover test architecture, including E2E, functional, unit tests, and manual testing. Special attention will be given to popular PHP testing tools such as PHPUnit, Codeception, Pest and Behat, as well as non-PHP testing tools such as Cypress, Playwright, CodeceptJS and Webdriver Bidi.

Are you tired of spending hours reading code just to find the right place to make a small change? Are you forced to split your application into several just so that devs don't step on each other's toes? This talk unites theory with practice to show you how to structure your code so that it is easy to read, to test and to maintain. You will step out with concrete ideas of how to improve your code design.