Too Many Tools and Frameworks (2015)
1–10 of 125 posts
Re: Too Many Tools and Frameworks (2015)
#2Ultimately the responsibility to pick reliable tools lies with the carpenter
Re: Too Many Tools and Frameworks (2015)
#3> "Using the same standards that categorize 90% of science fiction as trash, crud, or crap, it can be argued that 90% of film, literature, consumer goods, etc. is crap."
90% is also roughly the failure rate of startups. Pareto principle?
Re: Too Many Tools and Frameworks (2015)
#4I totally get what you are saying but it seems to be to be increasingly difficult to find the good frameworks, especially since the badness of some frameworks only manifest on larger scales.
Re: Too Many Tools and Frameworks (2015)
#5Ultimately the responsibility to pick reliable tools lies with the carpenter
The problem with that is that there are accepted standards for tooling for carpentry. Sure, there are 900 different kinds of tools, but they all solve a minimal subset of measuring, cutting, drilling, holding, joining, and smoothing.
There's no equivalent of the basic problems of carpentry in the profusion of javascript libraries. Many of the libraries written in the last year solve problems created by other libraries.
People forget that the reason Rails was such a revolution is that it took all the fifty kinds of crap that people used to build an application and made it available in one package with good defaults. The good defaults part of that is absolutely critical.
The problem is not "bad libraries", it's a complete lack of curation and direction.
Re: Too Many Tools and Frameworks (2015)
#6Ultimately the responsibility to pick reliable tools lies with the carpenter
True but most often the carpenter is misinformed by crowds or large corporation pushing their tools as "the best in the business".
Re: Too Many Tools and Frameworks (2015)
#7Light bulbs have not improved, they have become worse, and are designed to fail.
Re: Too Many Tools and Frameworks (2015)
#8For side projects, it can be a little daunting, but ultimately represents a healthy eco-system.
But the issue for me is how employers handles it. No, I don't know Angular. But I have used Backbone, Ember & React. So do you really need an Angular expert, especially when Angular is only a few years old and is completely changing in Angular 2?
Should employers insist on extensive trade knowledge in a specific framework, or should they be able to hire based on understanding of development and architectural principles, and give a new employee a little bit of leeway to get up to speed on their stack.
If it's the latter, then you can relax, and focus on reinforcing good practices and understanding the theory about what you're working on, and your resume will continue to build.
If it's the former, then you have to constantly pad your resume with skunkworks projects simply so it doesn't seem like you're getting "left behind." And that is exhausting, and not very useful to anyone.
Re: Too Many Tools and Frameworks (2015)
#9Ultimately the responsibility to pick reliable tools lies with the carpenter
On the other hand, a carpenter can buy a good hammer/set of chisels/block plane/circular saw - and use them for decades without cow orkers or project managers questioning their choice of tool and demanding they use completely different incompatible ones...
Re: Too Many Tools and Frameworks (2015)
#10For side projects, it can be a little daunting, but ultimately represents a healthy eco-system. But the issue for me is how employers handles it. No, I don't know Angular. But I have used Backbone, Ember & React. So do you really need an Angular expert, especially when Angular is only a few years old and is completely changing in Angular 2? Should employers insist on extensive trade knowledge in a specific framework,…
@michaelchisari honest question: are you a bit discontent with the fact that you don't know angular framework?