Is there a marketplace where one could buy a side project and post it on github? See a job add for a Go programmer, buy a Go side project...and so on.
As a teacher of mine used to say, you got there a business idea.
I have no side code projects to show you
161–170 of 545 posts
Re: I have no side code projects to show you
#162I’m not mad at you, but as the dude on the other side of the desk, I have to decide whether you can cut it and I’m fine saying no. I could make you do some whiteboard problems, but I think whiteboard problems are pretty far removed from your day to day development and I am uncomfortable relying on them as a proxy for your ability to ship code. I don’t really disagree with your philosophy of working while you’re worki…
On the flip side? As somebody who has plenty of open source projects--the set of employers who actually looks at them is within epsilon of zero. I have not once, not once gotten a meaningful question from anything I have posted on Github in any interview or client meeting even after suggesting up-front that it's worth taking a look. And I used to interview on a monthly basis just to keep in practice! No--instead you…
One company I work for rejected a candidate based on Github - he'd cloned some repos and stamped his name on it, and claimed they were his. The hiring tech smelled something fishy, and the candidate said that he worked with these various other repos on the backend. Hiring tech reached out to the owners of several repos, and none of them had heard of the candidate before.
Github was used in this hiring process to reveal a fraud - a different 'success' story to others commenting here, but it definitely birthed 'a meaningful question' or two.
Re: I have no side code projects to show you
#163It's funny that the tech industry is so insistent on side projects. I mean - would you hire a marketing person based on their 'side projects' or a corporate lawyer purely based on their pro-bono work? Likewise, who on earth asks a building contractor if they have any side projects? You would ask for references or find a contractor via someone you know. What about recruiters themselves? How does one judge if a person…
You know what's universally hard? Finding people who are good at their jobs. References don't matter, experience doesn't matter, education doesn't matter. Why not? Because it doesn't say anything about actual skill. What does? Side projects, where you can actually see if a person has skills. > a corporate lawyer purely based on their pro-bono work? You hire a corporate lawyer based on their public reputation. For a p…
Actually, the greatest predictor of employee success is their IQ, but that's illegal to test. That's why some employers substitute SAT, ACT, ASVAB, etc. scores, since those are abstractions to IQ tests.
Re: I have no side code projects to show you
#164What strikes me as weird about this is the assumption that it's an either/or proposition. I am passionate about playing traditional dance music. And I have supported this by writing a program to generate high quality sheet music from ABC scores; scripts to download collections of scores or MP3s off the web; scripts to handle tagging/naming my MP3 files; etc. I am passionate about RPGs. Back in the day I supported thi…
A lot of code you can't just toss up on Github. Is that your best code? It better be because that's all the code the interviewer is going to see!
Code quality is overrated in a side project. As developers we love to inflate this fantasy that someone else is actually judging our line-to-line code.
Unless you're incompetent and making glaring mistakes, someone reviewing your code would have to credentialize in your codebase to identify things like bad architecture. Nobody is doing that.
I'd put your energy into polishing a quality README. That's actually something that someone else will see, and I'd assert that it's the most important part of a project for someone flipping through.
In fact, in the hiring position, when I see someone with projects but not a single README, I have to wonder if it's a bad signal. Sure, they could do the easy part of slapping code against the wall, but they stopped before the hard part of documenting/introducing it. Something to think about when you're competing with other applicants for a job.
Re: I have no side code projects to show you
#165Earlier quoted context omitted.
You're espousing a false dichotomy. The options in evaluating a candidate aren't merely "give them whiteboard coding problems" or "examine their side projects". Give them a take-home assignment. Give them an in-person assignment where they have several hours to complete a smallish design-and-build task. There are a lot more options, and I'm getting tired of people claiming they don't know how to evaluate technical ca…
Giving a candidate a "take-home assignment" is actually the most disrespectful of the options listed. Unless you're an awesome company, with really cool projects and offering me a jaw dropping salary and benefits, then no, I'm not going to do free work for you. Even if you are an awesome company, people probably have to actually work for you to see that, so no, I'm not going to do free work for you. I'd rather spend…
You can actually achieve a happy medium between the two. About 2 years ago I interviewed with one of the large SF-based enterprise companies. They emailed me a cool little assignment (parse a text file that describes dependencies and build a graph, output install manifest) and asked me to send back a solution in an hour and half. An engineer was available to call on the phone to answer any questions, but otherwise I was left alone to code in peace, with no screen sharing or other kinds of watching as I coded.
It's probably the best phone screen/coding assignment experience I've ever had. No pressure from someone looking over your shoulder, but limited in time and scope, so I didn't spend all day working on it.
Re: I have no side code projects to show you
#166Earlier quoted context omitted.
When I look at a developer's Github profile I know that: 1. They care enough to have a Github profile 2. I can see their actual interests. 3. I know they're interested in random experiments 4. I can see if and how they treat their projects. Are they dedicated maintainers, or do they just fire off one-shot projects without ever deciding to maintain them? And a whole lot more. A person who maintains a single shell scri…
That's fair, thanks for explaining. To me it's fine to treat it as a huge bonus if the engineer can maintain a long lasting project with diligence. I just know a lot of people find side projects fun because they can let loose a bit and try out random stuff that may not be their "best" code.
>I just know a lot of people find side projects fun because they can let loose a bit and try out random stuff that may not be their "best" code.
This is still a huge asset. It's important for a person to want to grow and learn new stuff. When it comes to hiring a person, there's a whole lot of stuff that's important. Maintaining a long lasting project is one of them. Having an interested in fun side projects, also. It doesn't have to be good code. In fact, I have my fair share of "this project is not maintained and should not be used in production code" repositories. That's just shorthand for "this code sucks".
Re: I have no side code projects to show you
#167Earlier quoted context omitted.
There are also employers that downplay your achievements just to have a reason to offer you less money. The decision to hire you was already made and they advanced to salary negotiation but without telling you. You just have to know your real market value, how good are you compared to others.
Well, yeah. That's why, now, I run my own little consultancy. ;)
Thanks for mentioning this. I just finished a desktop app. They wanted to pay X but when the little app was done another colaborating company found out so I made 2.5 * X in total. Now the first company came back and they want another app for 4.5 * X. Is this how it all starts? :)
Re: I have no side code projects to show you
#168Unrelated to the topic:
I'm super excited about this guy, looking at his background we had to have worked in the same computer science lab at Texas State. We're the underdogs in Texas and it's cool to see people that were successful in the typical ivy-league environments. Incidentally enough, I'm now getting into mobile app performance and worked at Amazon around the same time.
Related:
I find that interviews are mostly a crapshoot. I'm currently looking for a new job in SF, so I have a few experiences from this last week that stood out:
* Onsite with a ~100 person startup last week where the guy asked about my past experience ("Wow me with a past project") and then I caught him looking out the window as I explained a particularly gnarly problem we solved at Amazon. I was asked 5 coding questions (that I more-or-less solved), never spoke to a manager and then got a canned rejection.
* Onsite with a ~2000-10000 person tech company and met my would-be team, my manager and his manager. We discussed the projects I'd work on, did coding and architecture problems and I left super excited to work with them in the future. I received an offer from them within a few days, having already built a relationship with my team and management, that makes me feel much better about the opportunity.
* I'm currently going through an interview with a really great company (~60 engineers). I spent an hour talking to my maybe-future manager and we left both excited to work together. The follow up was a realistic technical project and pair programming with my future teammates- all of whom were awesome to work with. I'm still awaiting next steps, but I've really enjoyed getting to speak to my future team.
A litmus test I've found: Does the technical hiring manager talk to you before you phone screen? Do they seem engaged and ask follow up questions? If your only point of contacts prior to the onsite is a random engineer interview and a recruiter whom repeats a script, your past work is not going to be a major factor. Most likely your hobbies outside work won't be considered (I'd suspect for legal bias reasons?) unless it's a small startup that's looking for a friend-as-a-coworker fit. I experienced this at my last startup, we went from 5 engineers to 50, and the values started to shift.
Re: I have no side code projects to show you
#169Earlier quoted context omitted.
On the flip side? As somebody who has plenty of open source projects--the set of employers who actually looks at them is within epsilon of zero. I have not once, not once gotten a meaningful question from anything I have posted on Github in any interview or client meeting even after suggesting up-front that it's worth taking a look. And I used to interview on a monthly basis just to keep in practice! No--instead you…
> Employers don't care. The wrong empoyers don't care. The right ones do. My github portfolio is a means for me to determine if a potential employer is suitable for me, not the other way around. It's not a test for me to pass, it's a test for a potential employer to pass. If a recruiter brings up things listed on my LinkedIn page, I know they're not suitable for me. If they bring up things on my github, I'm reasonabl…
You list things on linked in just so you can blame potential employers for looking at it? I dont even have linked in account and still find it ridiculous to hold it against them if they dare to look there.
Re: I have no side code projects to show you
#170It's funny that the tech industry is so insistent on side projects. I mean - would you hire a marketing person based on their 'side projects' or a corporate lawyer purely based on their pro-bono work? Likewise, who on earth asks a building contractor if they have any side projects? You would ask for references or find a contractor via someone you know. What about recruiters themselves? How does one judge if a person…
> It's funny that the tech industry is so insistent on side projects. I mean - would you hire a marketing person based on their 'side projects' or a corporate lawyer purely based on their pro-bono work?
I guess our field is so enjoyable that many people have side projects. Apparently, some recruiters think it's a good indicator of future success. I wonder if it's the case though. I teach CS and usually, passionate students (those who work on their own projects) are indeed better and spend much more time working on their assignments. But it's not the end of the story. For example, some are only motivated in things that involve coding, are stubborn, or are bad team players! Conversely, there are students who aren't hobbyist programmers but are smart, learn fast and are a joy to work with.