2 ms·
> solving DSA-style problems and building software are two different things disagree. I'd say that both are needed skills for software. Software is made layers
by bsedlm 5y ago
> solving DSA-style problems and building software are two different things
disagree. I'd say that both are needed skills for software. Software is made layers, like a cake. Maybe DSA style problems are like grounding the flour (or making the oven itself?) and the other building skills (which I agree, seem like different skillsets) are about decorating the cake and mixing the dough or something.
So in practice nobody is grinding their own flour; the flour is being bough already processed (in programming this'd correspond to importing the algorithms from a lib)
- buscoquadnary 5y agoI agree to a certain extent, it has been in my mind the big difference between impactful engineers and engineers that do a lot of stuff, it seems that many people can write code, but being able to conceptualize the software at the layer of DSA's allows one to flow fluidly from multiple levels of abstractions and aspects of the problem more seamlessly. That being said I also have serious beef with "architects" whose primary capabilities are programming in powerpoint and being professional XML developers.