3 ms·
if you're running a business there are good reasons to choose tools that are reasonably well known and widely used, regardless of whether they're the absolute b
by thwarted 12y ago
if you're running a business there are good reasons to choose tools that are reasonably well known and widely used, regardless of whether they're the absolute best available on the market. The biggest reason being that it's a lot easier to find developers who know or are interested in learning a popular tool than an obscure one.
Recently, I've been questioning the exact value of using popular tools because it's easier to find developers (vs other reasons). So much of what a business is building and providing is bespoke. Even if you use a popular framework that makes your job posting buzzword compliant, that can end up being a relatively small portion of the knowledge required to actually be effective writing software for your business's industry. This goes doubly for organically created internal business processes, which are, nearly by definition, bespoke and won't be found in exact form anywhere else. Now, if you've got good, strong project managers who know your business's industry (rare, IME), then maybe the primary knowledge/experience the programmers need is only on specific frameworks.
Obviously there's a lot of wiggle room here. Both early stage and established companies and code bases could make use of people who are either wide breadth or deep depth, there is no one guiding principle. Are you really going to turn down the candidate who knows 15 languages and frameworks but doesn't know the one you use? Or is this just your bias because you don't feel you'd be able to effectively interview them because you don't know as much as they do?
- cauterized 12y agoIt's not just about screening people for already knowing the tools. It's also about finding people interested in learning or using them. For instance, I'd imagine it's really difficult to recruit developers willing to work on software built in Cold Fusion if it's not already their preferred language. The same goes for anything new and sufficiently obscure. That limits your hiring pool significantly. And for the newer ones means you're unlikely to be able to find anyone with a deep understanding of your language or framework (or DBMS)'s internals.