|
|
|
|
|
by brosephius
5035 days ago
|
|
Sorry, I still can't agree with #1. It assumes that all workplace programming is gluing things together, fixing/maintaining legacy crap, or writing generic CRUD apps, which is untrue. I know some great programmers who never code in their spare time, and some that do that are, quite frankly, very uninteresting people to be around due to their lack of other hobbies. I know the current trend in startups is all about "show me your github", and I admit that it has some value as a filter, but I feel like I'm seeing people writing fairly uninteresting code snippets and blogs just to put it on their resume, in the same way that high schoolers join a bunch of student groups to beef up college applications. There are plenty of programming jobs that require writing complex code and having deep domain knowledge, and to discard those candidates because they can't show you their code and have other hobbies outside of work is just not smart. |
|
As I said elsewhere, I really like programming and will often do it in my spare time because it's fun. But needing to maintain some public repo or an open-source project in order to get a job makes it no longer fun.