I'm sorry, I was trying to be funny. I really found your points valid, and the helpful reminder was very appreciated as it will get me better answers next time.
I asked on purpose again for a couple of reasons: most of the answers were over 1 year old, most focus on why people shouldn't ask and not why they do ask or why they do sign.
Indeed, and learning to use a debugger will allow you to gain fluency in new languages and frameworks much faster that the simple, albeit powerful, printf.
I remember needing to learn Ruby and Rails on an existing closed codebase and having the debugger take me right to the core of Rails several times to understand why certain things were done in a certain way in the top level code. This allowed me to get acquainted with internals of Rails and how Ruby's inheritance system much faster as well as the existing codebase that was built on top.
I go as far as to have a dedicated project notebook for big new projects, I write everything down that I come across that I need to remember or need to question.
I've often been dropped into codebases where there is only a month to question the previous maintainer before all the business knowledge is lost as they move on to bigger and better things. So getting all the questions/queries down asap is the fastest step to get the undocumented business logic documented.
Even when you can't ask the questions I like to turn all the unknown unknowns into known unknowns. :)
“The Statements of Accomplishment (free) and Verified
Certificates (signature track) will be provided to all
those who achieve 50% or higher grade, and will be released
within 1-2 weeks after the final submission deadline closes.
Everyone will be notified by email when they are ready. You
will be able to download the certificate from your course
records after they are released.”
I think binary logging is the wrong word to use. As far as I can tell it's not binary he means, but database logging. Storing things in a database sounds far less scary than binary.
At best it's a NUL separated database structure where the fields are not compressed, which IS greppable just use \x00 in your regexp. At worst he might mean BER, which is an ASN.1 data encoding structure.
For passwords that change I use something similar to the Dominic mnemonic system to add a suffix to the password, this is for passwords that I really need to remember myself.
The pennies are obviously not to cover the cost of the MOOC. It the sunk-cost effect, people are more likely to use or complete something they pay for.
You can't make decisions about what will be standard in 10 years, however don't disregard the chance your software will be around in 10 years time.
I had a number of packages, written in 1998-1999 maintained in debian stable between 2000 and 2010, they were eventually dropped because they didn't work anymore after a big revisions in the parent project.
I did too, until I found.
http://middot.net/