Maybe it's because I'm not a software engineer, but I think the tone of these posts has been great. They are more why vs specifically how. I interview many engineers and I'm consistently surprised at how implementation focused they are and how poor they are at the why. I often ask the question "How do you design something?" and see it turn into a ramble of implementation details vs thinking about what problem they are trying to solve and why. Problem solving is the most undeveloped skill that I see as a whole. I find that people coming from non-engineering backgrounds will often have a better developed sense of this, but lack the experience to know strong implementations or design patterns, but they do a great job of understanding the problem.
Maybe it's because I'm not a software engineer, but I think the tone of these posts has been great. They are more why vs specifically how. I interview many engineers and I'm consistently surprised at how implementation focused they are and how poor they are at the why. I often ask the question "How do you design something?" and see it turn into a ramble of implementation details vs thinking about what problem they are trying to solve and why. Problem solving is the most undeveloped skill that I see as a whole. I find that people coming from non-engineering backgrounds will often have a better developed sense of this, but lack the experience to know strong implementations or design patterns, but they do a great job of understanding the problem.