I could imagine working in the industry professionally, it might become just as second nature to bean-count parts cost as say, to optimise compiled code size as a result of typically constrained memory environments.
Hobbyists who don't work in the industry, may yet aspire to in the future. So, would therefore be wise to develop that ethos, or - who knows - maybe that hobby project could later become something produced in high volumes?
Why needlessly limit a design, when designing something from scratch? It's rewarding to go for optimum goals. It'd be rewarding to aim to design an "optimum cost" system just as it would be for any other optimums one might target.
I could imagine working in the industry professionally, it might become just as second nature to bean-count parts cost as say, to optimise compiled code size as a result of typically constrained memory environments.
Hobbyists who don't work in the industry, may yet aspire to in the future. So, would therefore be wise to develop that ethos, or - who knows - maybe that hobby project could later become something produced in high volumes?
Why needlessly limit a design, when designing something from scratch? It's rewarding to go for optimum goals. It'd be rewarding to aim to design an "optimum cost" system just as it would be for any other optimums one might target.