3 ms·
A bit of a side note here regarding the author. Bruce Eckel's book "Thinking in C++ Vols 1 and 2"[1][2] was possibly my favorite book ever read. Bruce is (in
by freedomben 6y ago
A bit of a side note here regarding the author.
Bruce Eckel's book "Thinking in C++ Vols 1 and 2"[1][2] was possibly my favorite book ever read. Bruce is (in my personal opinion as an observer of people with zero professional training in psychology) a depth-first learner and naturally seeks to understand how things work by looking at the layers. Building up from there allows true understanding and even mastery of the material.
This is exactly how I am as well, and the result is often that it can take a while for me to pick things up and really understand them (since I have to cover so much more material than a typical person) but my level of mastery afterward is typically very high.
My experience now from well over a decade in the industry is that most people are not this way, and also that many people who are this way don't necessarily realize it. If you feel like understanding history, layers, etc helps you understand things much better, do yourself a favor and follow Bruce Eckel's blog and read his books. Thinking in C++ 2nd edition is 20 years old now. A third edition would be wonderful. Or maybe even better, "Thinking in Rust" :-D
[1] Volume 1 available for free on Archive.org: https://archive.org/details/TICPP2ndEdVolOne https://archive.org/details/TICPP2ndEdVolOne
[2] Volume 2 available for free on Archive.org:
https://archive.org/details/TICPP2ndEdVolTwo https://archive.org/details/TICPP2ndEdVolTwo
- Tainnor 6y agoInteresting observation. I feel like I am like that - I hate doing anything that requires me to develop only a superficial understanding (e.g. messing around with Kubernetes configuration without understanding how it all works on a fundamental level). I also don't like systems that are hard to debug - I want to be able to make assumptions and test them, and that can sometimes be notoriously difficult with cloud-based infrastructure.
- freedomben 6y agoInteresting you mention K8s, I had that same problem! It took me 6 months to get up to speed on K8s because I wanted to what everything meant, and those are all deep rabbit holes (like, try explaining the `apiVersion` in every object without going down a rabbit hole of how K8s works for example). Making that even worse there wasn't much out there to cover internals. The situation is much better now though. I guess that's part of price you pay to be an early adopter of the latest hotness.
- Tainnor 6y agoI still don't really know how Kubernetes works deep down, although I have learned enough to at least debug some of the most common issues I encounter at work, so if you have any very good resources (don't have to be free), I'd be happy to hear of them (the resources I've tried weren't very good, unfortunately).