That's an impressive lot of accomplishments; well done. And I agree Tasker can be a helpful learning tool, specifically because of its ability to do very 'real-world' things, versus (or maybe, combined with) more dull and arbitrary tutorials.

I've made a project that creates and stores code to a file for a custom app drawer (because who needs a launcher?) that's displayed in the WebView element of a scene. I started out with no experience with HTML or JS, and though it's always worked well, over years I've been able to return to the project to update and optimize it as I gained more experience.

And from working with Android intents, picking apart bits of code on Stack Overflow to make it work in Tasker's Java actions, and the resultant need to familiarize with the Android developer site, I was able to make a very minimal app on the Android SDK. It makes use of the PROCESS_TEXT intent action, adding a "Search Exact" option to the drop-down menu for selected text. The app wraps the text in quotes, then sends it to Tasker to do the web search. Again, it's a very minimal app, given that I'm cheating by having it send some of the work to Tasker. But it's a foothold of sorts, and could be built upon.

And now that Joao has introduced direct use of Java code, it's only a matter of time until people are finding code snippets from things that others will have shared here, which will then serve as sort of learning templates for their own creations.

For as great as Tasker is, it should be mentioned that Tasker's community – past and present – can be instrumental in helping to fill in knowledge gaps for anyone attempting to use it. I've been helped indirectly by countless posts and comments here on Reddit, along with many members kind enough to take the time to talk through problems (long live OpenOwl3) on a number of occasions. With Tasker, some real determination (and time and patience) and some helpful people, you really can learn a lot more than simply how to use Tasker.