7 ms·
"We've read your code"
- CWIZO 16y agoJust today I interviewed someone for a programming position. I asked him if any of his code is publicly available (a open source project, a small library, anything) and unfortunately he said no. So now I have to bring him in for a coding interview. It really saves a lot of time if you have something out there. Just make sure that the first thing one finds is something you want them to see (not some crappy code you wrote two years ago).
- scrrr 16y agoA friend was recently asked the same, also said no, and was declined the interview. He is a very capable software developer. It seems like being active on GitHub is slowly becoming almost a requirement in order to land a good job. I wonder if that is a good thing.
- chrisbroadfoot 16y agoBeing 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 :)
- jrockway 16y agoThe 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.
- CWIZO 16y agoI'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).
- dataguy 16y agoI 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.
- jonpaul 16y agoYa 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.
- Retric 16y agoI 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.
- jrockway 16y agoWhat 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.
- dalore 16y agoOnly 41 hours a week? Where do they work and are they hiring?
- fender 16y agoIt 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.
- cperciva 16y agoIt 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.
- xiongchiamiov 16y agoThere are of course large projects on GitHub, but your point still stands.
- nickelplate 16y ago"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.
- pierrefar 16y agoThe downside is when someone finds code you haven't touched in 10 years and would disavow now and think it's your current standard. So make sure you keep the home pages of such projects updated by saying "this project has been dormant since...".
- novel 16y agoMoreover, you have to be careful when uploading new code, when a new idea strikes into your head and you quickly implement a prototype, probably not in a very clean way and without unittests and stuff. This doesn't go well in conjunction with 'release early, release often' rule.
- IgorPartola 16y agoI think if you open source something it's kind of an obligation to clean up and comment your code at least a bit, job search or not.
- jrockway 16y agoIt's not. When sharing code, there is no obligation to do anything. More people will contribute and share if you have well-documented clean code, but if you just want to throw something up there, that's good too. Too many people don't contribute at all because the Internet is full of people looking gift horses in the mouth and they figure it's safer to not share at all. And that's not good for anyone.
- IgorPartola 16y agoSo sharing a crappy piece of code with poor documentation is better than holding out until you can release a tested product? I don't buy it. Case in point: the many terrible suggestions in the PHP documentation comments.
- salvadors 16y ago
- devmonk 16y agoWe don't all get the time to setup beautiful open-source projects with beautiful tests and code. I have a number of projects I've started or contributed significantly to that anyone can peruse if they want, but I'm definitely not proud of the code in all of them. If you use this type of post ( http://blog.jgc.org/2010/09/weve-read-your-code.html http://blog.jgc.org/2010/09/weve-read-your-code.html ) as a wakeup call to make your code better, that's fine. But, would it make sense to remove open-source projects that aren't your best work, with the rationalization that few if any are using them and they are a bad reflection on your coding skills? If your code is bad and is misleading/doesn't work and provides no benefit to others, take it down or fix it. Otherwise, I say leave it alone, and feel free to leave it attached to your name. I've met more developers who were afraid (imo) to start or share anything open-source even though they certainly could have (because I was working with them, and I did, without any harm coming to me yet). As Frank Herbert once wrote, "Fear is the mind-killer." Don't let the fear of sharing overtake you.
- IgorPartola 16y agoWhy not put up a message on the project's site saying that the code is old, unsupported and not really up to your standard anymore. Maybe list your current projects.
- IgorPartola 16y agoIn my last job search I put my resume on my blog (thereby refusing to send out Word files) and pointed potential employers to that, my OSS projects and my HN identity. Seemed to have worked :).
- edw519 16y agoThis works both ways. I have looked at other people's code and screamed, "Who wrote this &%*$^#?!?!?" Unfortunately, half the time it's my own.
- chegra 16y agoWhat is your github address?
- umjames 16y agoI think that means that all code you expose to the public should have the date it was created and last modified preferably in the files themselves. If your later code is better than the earlier code, it shows you're learning to program better.
- bullseye 16y agohttp://thedailywtf.com/Articles/Please-Think-Twice.aspx http://thedailywtf.com/Articles/Please-Think-Twice.aspx
- mgkimsal 16y agoThe flip side of this is a job I interviewed for (and actually did take) several years ago. I brought printed copies of some code I'd recently worked on (not sure why I didn't just bring a laptop!). Towards the end of the interview I brought it out and asked if the interviewer would like to review some of it with me. I was told "No". "Why not?" I asked. "Not everyone has the ability to bring code, and it would be unfair to look at yours if we can't look at everyone's." I was slightly flabbergasted, thought the logic was 100% wrong, but was offered the job and took it despite that. I was there about 2 years, and the first 18 months or so were generally enjoyable, but nothing lasts forever. :/
- InclinedPlane 16y agoThat's a pathological hiring mentality, it's not a contest, it's an attempt to make your company better by adding new talent. Good interviewers / recruiters use every trick possible to make sure they hire the best candidate.
- mgkimsal 16y agoThat's what I thought. But when you have an odd view of 'best', then you take odd steps. That episode sticks with me years later because it was the only time it's ever turned out that way.
- JoachimSchipper 16y agoSome blindness can help you find better candidates - not telling the recruiter whether the candidate is a member of <minority> may actually help quality (while decreasing information), for instance. Of course, in many/most cases, more information does help. But it's not automatic.
- saturdayplace 16y agoShortly after I started working my first real job, my manager had to attend training regarding how to hire and interview. One of the things they drilled into her was to make all the interviews as alike as possible. You MUST ask each candidate identical questions. Her impression was that this was to protect the company in the event an un-chosen candidate found about the differences and could find some grounds to sue. It's possible your experience sprung from the same lawsuit-averse well.
- yardie 16y agoIt's probably better to blast something out there so everyone can see it and possibly offer some advice. I've had plenty of things that were in the experimental phase and left at that. If someone really wants to see what I'm up to or what I'm interested in than it's far better to have said something than to remain quiet and invisible. I've met far too many programmers who are reluctant to share because they are ashamed of their code but quick to point out someone else's public flaws. It's just easier to criticize than be constructive. If someone isn't releasing memory properly ,in a public repo, then a 2-minute email will straighten that out.
- merijnv 16y agoDo people here think there's any importance to how professional/personal the domain name of your site is? For example, I registered inconsistent.nl (currently sadly empty because I nuked my web server in an experiment and still haven't gotten around to fixing it properly) because it fits my outlook on a lot of parts of the world. And as a bonus it works equally well as a Dutch or English domain. But other people keep telling me it is to unprofessional...
- jamii 16y agoI've been doing freelance work for enterprisey companies from the domain name scattered-thoughts and noone has batted an eyelid. I think for a personal website you're fine as long as its a name you would be comfortable explaining to a client. Obviously if the website is dedicated solely to your business its a different matter.
- kingkilr 16y agoBasically how I got my current gig, I knew my (now) boss from some open source work, they were looking for a contractor, and I had a job. No interview, no nothing, just a discussion of the terms and then down to business. Economists like to say complete information generates efficiency (or something to that effect), case in point.
- abstractbill 16y agoI've been lucky because "John Graham-Cumming" is close to a unique ID. When my wife and I got married, a couple of years ago, we decided to invent a new name for ourselves. I googled each alternative we came up with, and made sure the name we chose wasn't already taken. Sometimes you get to make your own luck!
- kragen 16y agoOurs was "Sitaker". What was yours?
- abstractbill 16y agoMoorier. My mother's maiden name is Moore, so we tweaked that a bit to make it sound French (my wife being half French).
- chaosmachine 16y agoPersonally, I'd be inclined to go the other way and change my name to John Smith. I'd rather not be easily Googleable by my real name. That's what handles and business names are for.
- acqq 16y agoYes, once you start to "promote" yourself your personality becomes "public" and different privacy conditions start to apply to you. Don't be surprised of the effects.
- presidentender 16y agoMy name is unique to begin with; I've taken further steps to own it on the internet. I made the mistake of tying it to this username, once, which has led (for better or worse) to a greater discretion under this username.
- gaius 16y agoJust for my own curiousity: was that your idea or hers?
- agentultra 16y agoYou're quite lucky then. I don't think I've been in an interview where the interviewer had bothered to read any of my code despite it being offered and out in the open. They don't even skim a few headlines from my blog first. I'm lucky if they know my name without reading my resume in front of me.
- mleonhard 16y agoI agree with the author that you will have more opportunities if your code is online. After graduating, I spent some time putting my personal and class projects on my website. Later in the summer I got a call from a dev manager who found my website accidentally when searching for programming info. He flew me out for an interview and offered me a job. The job offer gave me the courage to apply where I really wanted to work: Amazon Web Services. It also sped up the Amazon hiring process.
- benatkin 16y ago> And while places like Github and LinkedIn are important parts of your identity, there's nothing more important than a web site that you control. If you haven't registered your domain today, do it. There's a huge difference between Github and LinkedIn. You can put up content in any format at <username>.github.com. You get a local backup copy of what you put on their as a side effect of using git to push it. The contents of the repo doesn't belong to Github, so you can post it up anywhere. If GitHub disappeared (they won't) or took down your account for some ridiculous reason (they won't), it wouldn't take that long for search engines to be able to find the new location. If you can't think of an especially good domain name, I don't think picking one up today is a great idea. That said, I have firstlast.com and I recommend getting it to anyone who commonly goes by that combination and has the firstlast.com for their name unregistered. Finally, I'm surprised how many hackers are using HN or twitter but aren't active on GitHub. GitHub is at least 10x more valuable IMO. (You have to actively use it, of course, to get the value out of it.)
- patio11 16y agoMuch love for Github, but if I put my OSS projects there, I do not feel that I get value from them comparable to what I give up by not hosting it on my site. I also think hackers overestimate how many people will read your code (and if it were on your site, you could measure this).
- tjr 16y agoWhat do you give up by not hosting your projects on your own site?
- solutionyogi 16y agoLink Juice to your own site. I think Patrick's bingocardcreator.com domain did get good link love because he hosts his A/Bingo project (http://www.bingocardcreator.com/abingo http://www.bingocardcreator.com/abingo) on his own.
- 16y ago
- code_duck 16y agoYeah, so... if you put your code out there as open source, under your own name, a prospective employer might read it. Quite an insight.
- tdoggette 16y ago"We've read your code." "I'm so sorry."