Day 2
summary
Live demos focus on what actually changed and whether it worked: Juny agent edits code and runs tests (cloned Spring PetClinic, added logging, extracted service layer, ran tests and retried fixes but leaves some red tests); IntelliJ streams Gradle models during sync (project model from tooling API, KTS-targeted completions, extract-a-convention-plugin demo); Kafka shows Schema Registry storing schemas in an internal topic and Avro codegen for Java/Python/Node plus testcontainers for integration; JUnit ships Open Test Reporting with self‑contained HTML reports and parameterized test classes; JSpecify + ErrorProne/NewWay add gradual nullability checks; several talks demo prompt‑injection and RAG/vector poisoning risks.
AI-written summary · about
chapters (9)
- 0:00Intro
- 10:17"Sudo, Make Me a Sandwich!" – Live Coding With Agentic AI in IntelliJ IDEA by Anton Arhipov
- 1:11:09IntelliJ IDEA – The IDE That Speaks Gradle by Paul Merlin
- 2:10:06From Tower of Babel to Babel Fish: Evolving Your Kafka Architecture With Schema Registry by Viktor Gamov
- 3:09:43Catching Up With JUnit by Marc Philipp
- 4:09:52The Modern Database Debate: Documents, Tables, or Documents in Tables? by Franck Pachot
- 5:09:38Null Safety in Spring Applications With JSpecify and NullAway by Sébastien Deleuze
- 6:10:03Hacking and Securing AI Systems: Playing With Fire and Controlling the Flare of AI by Bar-El Tayouri
- 7:09:48OOP vs. DOP: Which One to Choose? by Venkat Subramaniam
