From time to time I have to hire a developer and since I started looking for type #2 I'm having a hard time.
I'm in the MS World and these kind of developers are really hard to find in our world. So, I usually I go with the type #1 and shoot myself in the foot because even if they do know their salt to get through most of small-internal-applications development most of them are unable to search, find or use popular open source libraries that can save tons of time and improve the performance of the whole app and sometimes even the whole company.
As a simple example I asked one of the candidates how they would build a small dashboard to show some e-commerce data and he came up with the idea of building an entire app from the scratch (including charts and client stuff) while simply using Dashing (what I ended up doind) would do.
I have no problem with developers who do not publish anything, but I do have a problem with developers who claim to be "senior" but always build everything from the scratch costing the companies thousand of dollars that might be spent somewhere else.
Plenty of companies are willing to spend the thousands of dollars building everything from scratch rather than rely on bought components they can't control or know entirely. Developers & management from that world may not know (or trust) available libraries; doesn't mean they're not "senior", it means their skillset may not match your needs.
The reverse complaint can be made: ask a candidate to build a small dashboard to show some e-commerce data - from scratch. If he can't do it without third-party libraries, is he "senior"? If he can do it, surely he's capable of spending a couple hours finding available packages to shorten the development cycle (saving time & money at the cost of reliance on outsiders).
Obviously you are a tech-business guy and practical I agree with u 100%.
I could tell you lots of stories about Super-UI-Architects, Evangelist Developers and crappy titles like that who claim to be the cream of the cream, don't bad judge me, they can be good and have a great knowledge, but they cost to your company a lot of extra money, time and headaches, usually are people who post code in github.
Those guys usually love to create the wheel again and again, they avoid to do the job in an easy way, just creating complexity. When I see a resume "Stuff-Architect, Something-Evangelist" I automatically send those resumes to the recycle bin.
Comments
From time to time I have to hire a developer and since I started looking for type #2 I'm having a hard time.
I'm in the MS World and these kind of developers are really hard to find in our world. So, I usually I go with the type #1 and shoot myself in the foot because even if they do know their salt to get through most of small-internal-applications development most of them are unable to search, find or use popular open source libraries that can save tons of time and improve the performance of the whole app and sometimes even the whole company.
As a simple example I asked one of the candidates how they would build a small dashboard to show some e-commerce data and he came up with the idea of building an entire app from the scratch (including charts and client stuff) while simply using Dashing (what I ended up doind) would do.
I have no problem with developers who do not publish anything, but I do have a problem with developers who claim to be "senior" but always build everything from the scratch costing the companies thousand of dollars that might be spent somewhere else.
Plenty of companies are willing to spend the thousands of dollars building everything from scratch rather than rely on bought components they can't control or know entirely. Developers & management from that world may not know (or trust) available libraries; doesn't mean they're not "senior", it means their skillset may not match your needs.
The reverse complaint can be made: ask a candidate to build a small dashboard to show some e-commerce data - from scratch. If he can't do it without third-party libraries, is he "senior"? If he can do it, surely he's capable of spending a couple hours finding available packages to shorten the development cycle (saving time & money at the cost of reliance on outsiders).
Obviously you are a tech-business guy and practical I agree with u 100%.
I could tell you lots of stories about Super-UI-Architects, Evangelist Developers and crappy titles like that who claim to be the cream of the cream, don't bad judge me, they can be good and have a great knowledge, but they cost to your company a lot of extra money, time and headaches, usually are people who post code in github.
Those guys usually love to create the wheel again and again, they avoid to do the job in an easy way, just creating complexity. When I see a resume "Stuff-Architect, Something-Evangelist" I automatically send those resumes to the recycle bin.