Might be just me, but I don't like part 1.3 at all. I think this content could go into an appendix or something instead. Probably the Task Flow content I edited out, too.
I highly, highly recommend explaining concepts only as needed and stick to practical actions that help a developer get a feel for what the code is doing.
What I'd like to see here is some instructions on modifying the task itself and using the debugger/logs to see how it's affecting the output. Like change the task to say something else other than hello world, having it play an audio file, open a web browser, something so people can get a more concrete understanding of what the task is doing.
Might be just me, but I don't like part 1.3 at all. I think this content could go into an appendix or something instead. Probably the Task Flow content I edited out, too.
I highly, highly recommend explaining concepts only as needed and stick to practical actions that help a developer get a feel for what the code is doing.
What I'd like to see here is some instructions on modifying the task itself and using the debugger/logs to see how it's affecting the output. Like change the task to say something else other than hello world, having it play an audio file, open a web browser, something so people can get a more concrete understanding of what the task is doing.
Happy to write it up if you want.