3 ms·
As someone also in the "editor > IDE" camp, I agree that a single monolithic tool is maybe the wrong path to take. But good coders still need powerful tools, j
by freshhawk 12y ago
As someone also in the "editor > IDE" camp, I agree that a single monolithic tool is maybe the wrong path to take.
But good coders still need powerful tools, just lots of tools, rather than one complex one. Simple and powerful are orthogonal.
I disagree that established industries have already optimized their tools. That's just blatantly untrue in real life, and for good reason. The tool makers always have the best tools. A journalist can't make a better tool for journalism without learning an entire new career (and tool making requires more experience than average as well, beginners don't make good tools).
- LukaAl 12y agoAgree on the need of powerful tool. And sometimes you ends up spending time writing the right tool for that specific tasks when it is missing (done more than one time). On your rebuttal on the tools for established industries, I just said that it's a suspicious claim, not that is false. The point is this: if an industry is a niche, usually who works in that niche has to build their own tools. In larger industries, like journalism, you think that a professional is not asked by toolmakers which feature they need to make their works faster or they don't approach themselves the toolmakers to ask for better tools? But let's see the problem from a different perspective. Could you list me an innovation that is just the application of a consolidated concept in an area to another consolidated area without a change on the underlying industry or of the technology. There's a lot of literature on this point. If you are interested, you could search for the Utterback S or the concept of paradigm shift in innovation.