I seem to keep reading what appears to be this nugget of wisdom about building solutions rather than coding but I can't tell if I'm missing something or if I ju

I seem to keep reading what appears to be this nugget of wisdom about building solutions rather than coding but I can't tell if I'm missing something or if I just consider the distinction to be sort of obvious. Can you please help explain? My reasoning is as follows. So if you're a programmer then you're in the business of building software solutions which are generally built via writing code or script of some sort. If the problem is best solved via a method other than writing software, then that's great. Not every problem needs software. Not every problem even needs solving either. If however the problem does need a software solution then it's obvious that you should make sure you actually understand the problem so that you actually solve it. I guess I just don't see how coding isn't equivalent to solution building unless what you call coding I call typing. For me thinking, researching, investigating, designing, engineering, planning, and even just "sleeping on it" are all part of the coding process. I suppose that if the purpose of your coding is to learn or play then you might not be building a solution. Is this just semantics or am I missing something?