The post gave the example of someone wanting to master a Mac Air - and as a result would have to read the 7 volume set of hardware documentation from Intel, the 5069 pages Application Kit Framework Reference etc etc
but that's only scratching the surface....
A recent post to the STC was from someone wanting to know what programming language to learn. So you can suggest something like Ruby and a book like Everyday Scripting with Ruby. A decent start
If all you're doing is throwaway scripts that might be enough Probably not though. Keep things organised and safe ? Time to learn yourself some Git
Want your scripts to be efficient ? Time to learn some programming concepts, maybe some Design Patterns
and you're working with the devs on ATDD/BDD/XDD so maybe an understanding of RSpec and/or Cucumber would be useful. There again, some people like Fitnesse, do you know enough about the options to be able to choose the most suitable one ?
and now you know some programming, maybe help out the devs and do some code reviews ? Not so fast, sonny - the devs have moved onto functional programming So time to Learn You a Haskell for Great Good or some Clojure ( warning, this stuff scrambles your brain on first/second/third reading )
Judging by the volume of questions posted to SQA StackExchange a lot of people are trying to use Selenium and it's likely you're doing browser testing in which case you'd better add that to your toolkit So if you don't want to spend your time asking questions and waiting for answers there then you'd better learn yourself some CSS, HTML ( oops, better add some HTML5 into the mix as well ), how to use Firebug
Hmmm, you're most probably using a database, how's your SQL knowledge ? Pretty good ? You can cope with Oracle or SQL Server or MYSQL ? and you'd be OK if the data solution is in memory like redis ?
Worried about the bad guys - can you explain to me how you've tested against XSS and MITM attacks ? Are you OK with using Fiddler to mess around with the network packets ?
There, that's the techy stuff covered... Except I've just read Adam Knights post about Testers Developing Their Technical Skills and realised I need to chat with the system admins and do some playing around with the operating system tools