Thank you! I enjoyed watching it. The way you write code & develop feels similar to mine, so it was nice to see..! - Appropriate layer separation - Core logic handled by services - Domain handles parts that need object responsibility - Writing SQL first before creating ORM persistence layer queries, etc. - Method placement, etc. I've been mainly using Line's JDSL recently, but I'm planning to apply Exposed to future side projects. I created one repo and kept updating to main without creating branches, so it's about 60 commits now! Now let me mention some areas that feel a bit lacking.. 1. Looking at the repo, it seems like you started in May 2024..! As of October 2025, Ktor is now up to version 3.3.0, so there are some changes..! Still, I think it would be great if you could add updates continuing from the last lecture about once every 3-6 months! 2. Besides global request/response interceptors, if there's common logic for specific operations, is there a way to apply it like Spring AOP? 3. If actually deployed to AWS, how much less CPU/RAM resources would it use compared to Spring..!? 4. Usually with JPA, we use Querydsl to handle dynamic queries safely, but I was disappointed that there wasn't coverage of how to handle dynamic queries in Exposed (only PathVariable, not dynamic queries created with QueryString) 5. For unit tests, slice tests, and e2e tests in Ktor, what's commonly used? I wrote about various things because I have many hopes..😊 Still, the course was really enjoyable to watch! I think I'll also consider Java with Spring+JPA+Querydsl(openfeign) and Kotlin with Ktor+Exposed going forward. Thank you.