Live data from Hacker News

If I can't see your work - you're crap

codingjohnson.com

1–10 of 64 posts

Re: If I can't see your work - you're crap

#2
Depending on the type of work you do your code would not go on github. If you write code for drivers for IR cameras in C or fix bugs in FORTRAN you won't be putting your stuff on Github or contributing to stackoverflow. Github/stackoverflow is, in my opinion, more catered towards the mobile/web/C# community. Military, medical equipment and aerospace software developers prob don't use it either one very much.

Re: If I can't see your work - you're crap

#3
I'd hire developer 1 for sure. I've never understood the idea that someone may be worse because they are employed and all the code they write is good enough to be paid for by someone else and thus can't be posted publicly for anyone to take.

Re: If I can't see your work - you're crap

#4
post #3

I'd hire developer 1 for sure. I've never understood the idea that someone may be worse because they are employed and all the code they write is good enough to be paid for by someone else and thus can't be posted publicly for anyone to take.

I agree but it's probably worth noting that those who come from developer group #1 probably won't have to demonstrate Github repo's or blogs anyway, because the large companies that they are working for don't really care about that the way the smaller upstarts do.

Re: If I can't see your work - you're crap

#7
I use private repos on Bitbucket. Most of what I've worked on over the last 5 to 10 years my competitors would absolutely love to get their hands on. Much as I'd love the street cred, I can't publish my code. If the software is an important part of what gives me an advantage over my competitors, then I can't publish the code. If it's written for a client, I can't publish the code. Really, there's only a very narrow spectrum of circumstances under which code can be given to the public. Computer software runs all facets of our lives, and very little of it is publicly available on github.

How about this. If you make sweeping generalizations without thinking things all the way through, you're crap.

Re: If I can't see your work - you're crap

#8
post #2

Depending on the type of work you do your code would not go on github. If you write code for drivers for IR cameras in C or fix bugs in FORTRAN you won't be putting your stuff on Github or contributing to stackoverflow. Github/stackoverflow is, in my opinion, more catered towards the mobile/web/C# community. Military, medical equipment and aerospace software developers prob don't use it either one very much.

I don't see the parallel between github and Stack Overflow. I can understand why programmers in certain industries and companies won't be posting their code on github. If all of the code you write professionally is proprietary, it makes sense that none of it would wind up in github public repositories. But even if I'm writing proprietary code, I can still ask questions about it on Stack Overflow, and answer other people's questions.

Re: If I can't see your work - you're crap

#10
I fall into the "developer 1" category myself. I only recently started doing side projects in my own time (and publishing them on github), almost entirely because I was starting to run into walls job searching without a "portfolio." Unfortunately, this means that what potential employers are seeing is stuff that I've done in my almost non-existent free time, so it's generally unfinished, unpolished projects that had a really simple goal or were for learning a new language/framework. So, it's not necessarily a good indicator of what I produce when I can focus full time on a project.

It sucks that I am "punished" because all of my actual work has been for companies that aren't interested in sharing their products with the community. I've even tried a few times to get tools I've created released as open source, but the general response I get is, "uh, why?" I can understand that the companies see no value in it and in fact may cost them money if there end up being licensing or other legal issues.

Post reply on HN