Simon Verhoeven

Hello Barry, I was more wondering whether the book also offered advice on teaching or if it's focused on those learning the language themselves.

I was wondering if the latest version also tackled teaching Java to beginners, and the impact of recent JEPs (in preview).

I was thinking of the Corporate Sustainability Reporting Directive and similar initiatives @Campbell Ritchie.
Not so much legal problems, but things we need to keep in mind and tackle proactively.

I was wondering if certain regulations were also covered, or if the core focus is the development.

I was wondering whether less frequently thought of use-cases/libraries were also covered such as picocli for terminal user interfaces.

I think Helidon offers a lot of benefits and opportunities, but one challenge I often encounter is that people tend to default to the older/de facto used frameworks rather than evaluating the benefits. So I was wondering if this was addressed, and the specific benefit of Helidon SE/MP.

I'm always curious about how far ahead of time you start writing these study guides, especially with the next LTS in mind where we'll have some pretty significant changes when one even looks at the JEPs in 24 that are likely to land in 25.
Or maybe a slightly more "depressing" variant, how early do you start preparing content for a specific topic, which might still get dropped such as String templates?
Given the scope of the exam writing these always looks like such a daunting task to me.

I was wondering what the envisioned target audience was. Is it more for someone transitioning into a more architectural role, or is it also a good fit for junior developers in general with a keen interest in proper architecture?

A lot of books on this topic stay a bit too abstract and too narrow to make them easy to digest for my colleagues.
Personally, I believe in a more hands-on, iterative approach myself. So a more practical book is always of interest to me.

I was wondering if the book also dives a bit into when it's a (not) so good fit.
When one might consider staying with a standalone UI/wicket/Vaadin Hilla.

I was wondering how much of the focus was on how to do X (at times the documentation can be, let's say interesting) versus pitfalls you've encountered/recommendations.

I was wondering whether this book/chapter also shed some light on k3/istio/helm/nomad/...

That's indeed always the question, and thank you for the swift reply.
Linking to things on the horizon/teasers indeed sounds like a good approach.

I was wondering if this book already covers certain new possibilities for FP using the functionality currently in preview mode.

Sorry, I might have worded it poorly. I meant it more in the sense of: aspects that were originally expected to stay a bit longer in incubation/preview due to feedback that still end up in the LTS version (since like Vasily mentioned only LTS get exams, on that front ) since some features are quite extensive scope wise, and it's quite a weighty book already literally and figuratively. Also with the shift from 3 => 2 years for LTS.

When do you generally actually start on the preparation for the next LTS exam guide, given I can imagine it's quite an extensive process given the scope of the material.

I was actually a bit curious about the writing process for an author for one of these, since I can imagine the swifter release cycle (especially now) poses quite some opportunities/challenges. So I was wondering how you dealt with these, especially with (preview) features that get added relatively late in the cycle.