Being a software engineer, I have a different perspective. I tend to not trust books, video, or other forms of documentation. Unlike hardware which has a much greater specification longevity, what is true about software today is probably obsolete in 3 months (the Linux APIs being a notable counter-example).
So, my favorite learning tool is the source code + README files (if available). Frankly, knowing how lazy programmers are about documentation, I take comments in the source code with a large grain of salt.
Okay, you probably guessed that I have been writing code since the days of punched cards. Good documentation is my post-it system, especially for assembly language programs.
Being a software engineer, I have a different perspective. I tend to not trust books, video, or other forms of documentation. Unlike hardware which has a much greater specification longevity, what is true about software today is probably obsolete in 3 months (the Linux APIs being a notable counter-example).
So, my favorite learning tool is the source code + README files (if available). Frankly, knowing how lazy programmers are about documentation, I take comments in the source code with a large grain of salt.
Okay, you probably guessed that I have been writing code since the days of punched cards. Good documentation is my post-it system, especially for assembly language programs.
Top Comments