3 ms·
actually, nearly all developpers like to build things from scratch. The real difference is, as noted in the article, the one who will use the right tool for the
by h1fra 11y ago
actually, nearly all developpers like to build things from scratch. The real difference is, as noted in the article, the one who will use the right tool for the job and the one who take "from scratch" literraly.
I see many people, doing 'from scratch' the same things for years just for the sake of it. Without realizing they are wasting time and introducing the same bug/mistake because they can't learn anything new. And when you present them framework, library or snippets, they are reluctent to learn or simply discover them.
I find the lack of curiosity and self questionning very disturbing, for a community that introduce themselves as rockstars and elite of society.
So a developper that can from scratch is for me, actually less interesting than a developper that know how to reinvent himself.
- JshWright 11y agoThat was my first thought as well... I find it's pretty rare to find a developer that is excited to work on someone else's bugs...
- cellularmitosis 11y agoGenerally, I agree with what you are saying. However, there is one example of someone speaking to the opposite view which I also agree with: Marcus Zarra: https://vimeo.com/97058344 https://vimeo.com/97058344 I think the key there is that he is in somewhat of a niche: client-side iOS programming. By limiting the set of problems which he is reimplenting "from scratch" again and again, he has some hope of getting very efficient at the "from scratch" approach (he becomes an expert in that approach). I also think this approach is probably only realistic for very small slice of people (top-level talent whom are also lone-wolf contractors (no oversight, no collaboration)).