3 ms·
> knowledge of existing libraries, algorithms, systems, permissions I can't help but notice, also, that no project management "methodology" emphasizes (or even
by commandlinefan 8y ago
> knowledge of existing libraries, algorithms, systems, permissions
I can't help but notice, also, that no project management "methodology" emphasizes (or even allows for) time spent researching/learning existing libraries, algorithms, systems, permissions, even though I think everybody would agree that this is where you're going to get the biggest payoff.
- pentagonpapers 8y agoI think waterfall can, by having serious scoping discussions.
- pas 8y agothat's bollocks, and I phrased it nicely. every pm methodology talks about getting to know the problem domain, risk minimalization (start with the riskiest assumption, do a minmax check on it, the pivot to the next riskiest, and so on). selecting the right tool for the job is an inherent part of the process.
- PakG1 8y agoIt is, that doesn't mean that people do it. :D
- erikb 8y agoI'd say the direction you are going is correct. And I would add that the big payoff is in understanding of fundamental problems, not libraries or algos. For instance you should know how TCP/IP works and HTTP works (not just theoretical but hands on, i.e. know when to use curl, when the browser and when tcpdump for debugging). But you don't need indepth knowledge of the currently hip web framework because in 5 years it won't be hip anymore.