Hey, @altavir I have seen in many places you recommended using Gradle and you are a huge fan of it. As a beginner, I tried to understand Gradle and I sort of understand it but sometimes it feels weird.
Gradle is simply a collection of tasks. And every plugin provides a set of tasks to be performed. That's the basic explanation provided in all the beginner level docs. However, after stating that, the docs move straight to describe the usage of some kind of plugin to achieve a specific goal like compiling a kotlin source or creating an Android build.
I haven't been able to find any tutorials that shows the code compilation from the command line and walk upwards by creating Gradle tasks to achieve the same.
I am pretty sure this is really simple. That's why no one even bothered to create a tutorial on it. But whenever I talked with any beginner who is using Gradle I found that nobody knows how to do this. And their (including myself) understanding of Gradle is very shallow.
For example, beginner people know what Gradle is doing but they don't have any idea on how they can write Gradle tasks to do the same thing without any plugin.
That's why we are heavily relied on copy pasting from the docs when it comes to using Gradle.
It would be really helpful if you can come up with some articles that take a bottom up approach on explaining Gradle.
I found a book named "Gradle in action" but that is so backdated that the code snippets doesn't work in modern versions of Gradle.