For the past year I've had my head buried in Spring Boot for Java, and now Kotlin. A developer approach that I've always followed is that before introducing novel approaches, patterns, recipes, etc. is to implement a bare bones skeleton project first. This is essential to get that "clean room" validation that can prove assumptions, crush them if necessary. But most importantly it can be done in a way that is "as few things as possible" to ensure I understand what is going on.
This is also helpful in tightening the developer loop in the early discovery part. Your brain requires lots of cycles of trying, failing, trying, failing. So, sitting and waiting for a larger app to startup, etc. is Flow killer. Why hurt yourself? Developer Loop is one of my critical areas of focus on what I try to add as value on projects. Make the developer experience "better".
Spring Boot is an extensive platform and framework. Configuration is at the core along with all the helper areas. So, when I'm scaffolding a quick solution, I hate wasting time. Surely, I can do this inside of JetBrains IDE or using the Spring Boot Initializer site - but another cool thing is you an issue a web request (via curl or your favorite tool) with the proper set of parameters and you get a tar Gzip file that you just decompress – then you're off and running.
An alternative is via a URL as follows, which provides the same as above, just the query string parameters are explicit curl parameters above.