3 ms·

I feel you. I think this is due to the fact that the overall concepts are usually quite easy to understand and therefore easy to talk about. As soon as you ha

I feel you. I think this is due to the fact that the overall concepts are usually quite easy to understand and therefore easy to talk about. As soon as you have to dig deeper you need to invest significantly more time to talk about it and your audience becomes really small. This is amplified by people creating newsletters, content (marketing) in general, but the actual knowledge/wisdom is not given away. It's incredibly frustrating but happens in almost all technological field, especially when they are fast moving. In mechanical engineering for example a lot of wisdom is also put into norms, standards and so on. Books are written about it. But 10 year old books are still completly valid while in software every couple of years a new framewokr is the new hot shit.

Swizec 4y ago
> But 10 year old books are still completly valid while in software every couple of years a new framewokr is the new hot shit The more I look at it, the more it feels like software hasn’t had a fundamentally new idea in decades. Frameworks improve, networks get bigger, compute gets cheaper, and we spend most of our time dealing with domain modeling, cache, and statistical inference. We’ve made great strides in the ease of building and encoded many lessons in our frameworks, scale is bigger too, but the underlying guts of software engineering have been very stable for decades.
- Shinmon 4y ago
  I agree actually...kind of. And there are good books about software architecture and so on. Unfortunately, for each good one there are at least 50 that are really really bad. There are a lot of technology-related books as well, that teach you about responsive web design with react or stuff like this. Encoding lessons in frameworks isn't always helpful either in my opinion. Your mental model of the software needs to be correct, otherwise it's just a really painful experience. What works for large scale software is often just pain for beginners.

Swizec 4y ago

> But 10 year old books are still completly valid while in software every couple of years a new framewokr is the new hot shit The more I look at it, the more it feels like software hasn’t had a fundamentally new idea in decades. Frameworks improve, networks get bigger, compute gets cheaper, and we spend most of our time dealing with domain modeling, cache, and statistical inference. We’ve made great strides in the ease of building and encoded many lessons in our frameworks, scale is bigger too, but the underlying guts of software engineering have been very stable for decades.

Shinmon 4y ago
I agree actually...kind of. And there are good books about software architecture and so on. Unfortunately, for each good one there are at least 50 that are really really bad. There are a lot of technology-related books as well, that teach you about responsive web design with react or stuff like this. Encoding lessons in frameworks isn't always helpful either in my opinion. Your mental model of the software needs to be correct, otherwise it's just a really painful experience. What works for large scale software is often just pain for beginners.