What is best practices reading a new programming language book considering:
- You are working full time
- You never used that programming language
- Your work environment is not using that programming language
|show 1 more comment|
Questions on Programmers Stack Exchange are expected to relate to software development within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
If you are a morning person:
If you are an evening person:
I do something similar to what Matthew Flynn suggests - I have the book (either printed or in e-book form) open, read it, type along, and experiment on my own until I know how to use what I just learned without constantly looking it up.
One thing I do, though, is use a language that my company doesn't officially use, as a rapid prototyping language. I work in a .NET environment at work, and I use a lot of Python/R to do my work before writing a line of C#. I am looking into setting up IronPython and F# to get direct access to the objects/assemblies that my C# environment has.
Facilitates learning, lets me experiment faster.