I’m opening my workshop “Concurrent Programming Fundamentals for the AI Era” to external teams for the first time. Concurrency isn’t really about algorithms or APIs. It’s about being able to look at code and see what can happen between threads or coroutines, and how to prevent possible races and bad interleavings. This intuition is the hardest thing to teach. Over the past 8+ years, I’ve taught concurrency at universities and later turned that experience into internal workshops at JetBrains. I ran the workshop several times for 250+ colleagues and received overwhelmingly positive feedback, with many participants saying it changed the way they reason about concurrent code. In the AI era, this skill matters even more. AI can generate code quickly and confidently, but subtle concurrency bugs still need human understanding, careful testing, and debugging intuition. It’s a 4-day, hands-on workshop for JVM developers. Participants implement classic and modern concurrent data structures, dissect tricky bugs, and learn practical testing and debugging techniques in Java or Kotlin. I’m now looking for the first external teams who’d like to try it. If your team works with backend systems, infrastructure, databases, developer tools, coroutines, virtual threads, or other concurrency-heavy software, I’d be happy to talk. 👉 Details: nikitakoval.org/workshop