[weland]

I, for one, cannot remember any training, workshop or course that didn't have at least half an hour of obvious, blatant corporate agenda crap and here's-why-you-don't-need-any-technology-other-than-this-one. Some of them subtly painted, but generally that. In time, I simply stopped attending any. Whenever my employer needs me to learn something new, I end up suggesting buying me two books on the subject and letting me take three days off to study them. Cheaper and far more efficient.

I don't know what they're covering in the chapter about the Linux foundation, but the second chapter sounds extremely useful to me. A lot of people who come from a Windows or often an OS X background don't really grok:

* That you can -- and should -- chain program together, not rely on the feature set of a single one

* That, when in doubt, you can look at the source of the program if you can read it

* That there are other release models at work other than "One major version ever X years and $osnameUpdate in between", and you need to know what you can expect from each

* That the kernel and various bits of userspace are separately developed and packaged, which has repercussions over what practical systems look like.