Hi! My name is Roman. I am a JVM backend developer with about 8+ years of experience, and I find concurrency one of the most interesting parts of software engineering.
That interest did not appear right away. It came with experience: production issues, code reviews, and backend interviews at companies of different levels. Over time I started to see how complex and diverse this topic really is, with its own patterns, trade-offs, and tools.
Thread Traps is my attempt to structure practical problem patterns that almost any backend developer can run into. I want it to help engineers spot possible performance bottlenecks faster, choose the right JVM concurrency tools with more confidence, and review code more carefully, whether it was written by an agent or by a colleague :)
I decided to start with the basics of single-instance Java concurrency. Later I plan to expand the site with Kotlin patterns, examples that bridge Java concurrency tools with Kotlin approaches, and an interactive quiz mode for checking your knowledge.
If you have suggestions for correcting cards, adding scenarios, or any other kind of feedback, feel free to create a PR or write to me by email.