"We've read your code"

Re:"We've read your code" by dataguy on Monday September 20, 2010 @07:36AM (#1708423)

I like your last sentence. I am also sceptical if this is a good thing. And with reason: If you are working as a skilled software architect - and you work on projects under NDA or other laws/contracts for a long time, it could definitely come to the result that you do not have "current code" somewhere out there on github and such sites. And not everybody has the time or the reason to contribute or start an open source project. That even becomes more critical if you want to do other things in your non-working time than coding. If you have the chance to work for a company where you are allowed and instructed to work on open source projects and technology, then you are lucky. But I doubt that the major of software designers does so.

[ Parent | on HN ]

Re:"We've read your code" by jrockway on Monday September 20, 2010 @08:18AM (#1708507)

What does he do with the other 16 hours of his day? If I can hire someone who spends 41 hours a week programming, with 1 hour of work that I can actually see, that is going to be a big advantage over someone who claims they are a super-genius architect. Because the first person has documented proof of ability, but the second person just says he's really good.

Don't worry, though. I work with "C++ experts" who don't realize you have to allocate memory before writing to it. Knowing how to program is not a prerequisite to all programming jobs.

[ Parent | on HN ]

Re:"We've read your code" by philf on Monday September 20, 2010 @08:51AM (#1708581)

I suppose you also need to sleep, so that's 8 hours left of which you spend some preparing/eating food, maybe some sports every once in a while, shopping, socializing etc. Anyway, I'm pretty sure there are people who, while having a passion for software development, feel like doing something else for a change after 8 hours in front of a computer.

[ Parent | on HN ]

Re:"We've read your code" by yummyfajitas on Monday September 20, 2010 @10:55AM (#1709021)

If you sleep 8 hours/day, that leaves you with 112 waking hours/week. After work, 1-2 hours of sports a day, you've still got about 50 hours/week.

You can't devote even 2% of that time to building a portfolio and helping possible future employers to evaluate your skills?

[ Parent | on HN ]

Re:"We've read your code" by nickelplate on Monday September 20, 2010 @06:23PM (#1710711)

"Because the first person has documented proof of ability"

I think this really depends on the position you are trying to fill. A track record of shipping code to customers counts for a lot more in my eyes than open source code (unless we're talking about something really high profile like Firefox or llvm). A lot of really talented and passionate developers are plenty challenged and stimulated at work that they don't feel the need to work on hobby projects in their spare time. What could these people write in one hour that would be of significance?

[ Parent | on HN ]

Re:"We've read your code" by dalore on Monday September 20, 2010 @08:38AM (#1708549)

Only 41 hours a week? Where do they work and are they hiring?

[ Parent | on HN ]

Re:"We've read your code" by jrockway on Monday September 20, 2010 @08:51AM (#1708582)

Anywhere? I've never had a job that required more than 40 hours a week.

[ Parent | on HN ]

Re:"We've read your code" by billybob on Monday September 20, 2010 @09:43AM (#1708746)

Some jobs don't "require" more than 40, but when your fellow developers are always there earlier and later than you are, and when your performance reviews go from bad to good after you ratchet up your number of working hours, and when your assignment list keeps growing longer and more urgent, you get the message.

[ Parent | on HN ]

Re:"We've read your code" by dpritchett on Monday September 20, 2010 @10:36AM (#1708944)

This is probably a sign to change your situation. Start working 40 hours a week, expect bad reviews short term, build a huge open source portfolio using the extra 10-20 hours/wk you've created for yourself by opting out of the sick system.

Next year, you have a better job elsewhere.

[ Parent | on HN ]

Re:"We've read your code" by jrockway on Monday September 20, 2010 @01:31PM (#1709691)

This means it's time to change employers and get your 30% raise.

[ Parent | on HN ]

Re:"We've read your code" by jonpaul on Monday September 20, 2010 @08:08AM (#1708488)

Ya but I think you're missing an important point. Having an active Github can demonstrate a developer with passion instead of one who just sees it as a job.

[ Parent | on HN ]

Re:"We've read your code" by Retric on Monday September 20, 2010 @08:54AM (#1708593)

I know way to many passionate, articulate, and terrible programmers to think passion a good thing. I also know plenty of really great programmers who don't find coding a challenge after all these years. On average I think passion speaks more to youth than the ability to get things done.

[ Parent | on HN ]

Re:"We've read your code" by raghava on Tuesday September 21, 2010 @08:07AM (#1712268)

>>work on projects under NDA or other laws/contracts for a long time

There are firms that actively ask people NOT to post code outside (citing IPR); and at times, even go ahead and mention that anything a person on it's payroll writes (even if written in leisure time or at home off work), belongs to the firm. The 'extended workplace' clause in terms of contract could be suitably flexed.

[ Parent | on HN ]

Re:"We've read your code" by cperciva on Monday September 20, 2010 @10:26AM (#1708907)

It seems like being active on GitHub is slowly becoming almost a requirement in order to land a good job.

You know, there is open source software which isn't on GitHub.

Personally I'm far more impressed with someone who has a commit bit on a project like FreeBSD, because it shows an ability to work together with other people. Having code on GitHub just shows that you're able to fork someone else's work.

[ Parent | on HN ]

Re:"We've read your code" by xiongchiamiov on Monday September 20, 2010 @06:53PM (#1710780)

There are of course large projects on GitHub, but your point still stands.

[ Parent | on HN ]

Re:"We've read your code" by chrisbroadfoot on Monday September 20, 2010 @07:17AM (#1708403)

Being active with open source communities is definitely a huge advantage, but I wouldn't go as far as to say that you need to be active on GitHub. There are other ways to contribute open code :)

[ Parent | on HN ]

Re:"We've read your code" by jrockway on Monday September 20, 2010 @08:19AM (#1708509)

The ideal candidate will do both. It's fine if you just hack other code, and it's fine if everything you make is 100% your own. But the best programmers do both.

[ Parent | on HN ]

Re:"We've read your code" by nickelplate on Monday September 20, 2010 @06:30PM (#1710730)

"A friend was recently asked the same, also said no, and was declined the interview."

I think that's retarded. There are more effective ways to filter out bad apples. Candidates could be asked to solve a puzzle and attach their solution to their application, for example. Most of the really good developers I know stopped coding in their free time after accumulating about 5-8 years of experience. They have other commitments (wife, kids...) and their day job is challenging enough as it is.

[ Parent | on HN ]

Re:"We've read your code" by fender on Monday September 20, 2010 @08:24AM (#1708521)

It happened to me but I was given a chance to prove my worth to them. It was a small company (basically a start up) , To cut the whole thing short I ended up with a job and worked with them for 2 years.

[ Parent | on HN ]

Re:"We've read your code" by CWIZO on Monday September 20, 2010 @07:33AM (#1708421)

I'd never reject someone on that point alone. I'm guilty of not having anything (at least not something I'd like to show) out there too (thou I am working on it).

[ Parent | on HN ]