Exactly. I'm not saying that you should go back to code in assembly. But, come on, you can surely dedicate 30 minutes of your time to read how a CPU works... Just have curiosity would be my advice
At the expense of what, though? That's 30 minutes not spent learning about the business, or talking to customers, or to your kids. Or watching the World
Cup. Or reading Hacker News.
i always hear this argument. and then those that proclaim it get stuck for a sprint trying to fit a square peg in a round hole
and then i get a ticket a month later because the customer reported the feature isn't working. all while they proclaim how much they care about the customer.
i'm not just talking about one person. i feel as if there's an archetype of programmer that thinks like this.
I'm not sure what archetype my comment makes me fall under, but my point is people spend time and effort learning about the things that are important to them. The things that are important to them aren't important to you and I'm saying that being interested in how a CPU actually works doesn't make you better or smarter than them being interested in how other parts of the business work.
