More on Reading and Writing Books
Russ White wrote a great response to my “Do You Really Want to Write that Book?” blog post and I couldn’t agree more with what he wrote. Unfortunately, he seems to be a bit over-idealistic when analyzing why the market for high-end content is so small.
You know I usually have a cynical explanation handy, so here it is: too many people calling themselves engineers for no particular reason simply don’t care. It’s way easier to Google-and-paste your way around than to invest time in understanding the fundamentals.
I understand that you won’t devote days to studying technologies underlying a simple problem that you have to solve once in a lifetime, but if you encounter the same challenge multiple times, it’s time to do some proper research.
The problem with the scenic route to knowledge is that you have to invest an extraordinary amount of time before reaping the benefits (see also: 10K hour theories), but once you do, the results tend to be great.
For example, it’s really easy to identify the problems with most things touted as SDN once you’ve seen (and understood) enough networking technologies – there are only so many ways a problem can be solved, and I haven’t seen a revolutionary one in decades (regardless of what the marketers trying to separate VCs from their money claim).
To summarize: Don’t be one of the people interested in finding shortcuts (aka Best Practices) without understanding them. Whenever you’re trying to grasp a new technology ask simple questions like:
- WHAT problem is it trying to solve?
- HOW does it work (as opposed to How do I configure it)?
- WHY does it work the way it does?
Before you leave: If you made it this far, you MUST watch the excellent A Praise for Hackers Troopers 2016 keynote by Rodrigo Branco.
And finally: if you prefer watching videos over reading books, here’s a treasure trove of 130 hours of downloadable videos.
Most companies want people who fix problems (fast).. not who understand the problem.
Also in order to save money, they prefer to hire fewer people with lower quality. This kills the motivation for people to learn and to understand the problems and just know the necessary stuff to get the job..
It is also common to make technical decisions on management level, leaving the engineering with the question "how do i configure it to make it work"
This all leads to many people relying on google to quickly fix the problems instead of spending time and reading books to understand it.
http://www.amazon.com/SDN-Software-Networks-Thomas-Nadeau-ebook/dp/B00EJX7WEG/ref=tmm_kin_title_0?_encoding=UTF8&sr=&qid=
http://www.amazon.com/Principles-Practices-Interconnection-Networks-Architecture-ebook/dp/B001V7U76I/ref=tmm_kin_title_0?_encoding=UTF8&sr=&qid=
http://www.amazon.com/gp/product/0321193687/ref=olp_product_details?ie=UTF8&me=
http://www.amazon.com/Building-Microservices-Sam-Newman/dp/1491950358/ref=sr_1_1?ie=UTF8&qid=1434218480&sr=8-1&keywords=building+microservices
http://shop.oreilly.com/product/0636920032885.do
:-)
Russ