Good read! My similar technique (though webdev focused) is to:
Get a working dev environment
Learn the absolute basics of the language syntax
Learn how the request-response pattern is implemented in that language/framework
The most important part: build a familiar full stack project (ex. Twitter clone)
Most of the meaty parts such as ORMs, 3rd party APIs, frontend setup, testing environments, more advanced language constructs etc... will be tackled on the go as I build the project. I think this is a good compromise between strictly studying the language vs diving deep into a project without any plan.
Good read! My similar technique (though webdev focused) is to:
Most of the meaty parts such as ORMs, 3rd party APIs, frontend setup, testing environments, more advanced language constructs etc... will be tackled on the go as I build the project. I think this is a good compromise between strictly studying the language vs diving deep into a project without any plan.
Thanks for the feedback, I really appreciate that ;)