3 ms·

I’ve seen way too many “experienced devs” who are terrible coders.

by hamandcheese 5y ago

ipaddr 5y ago
In the end prioritize for the position. If you want good coders look for resumes with startup experience. You don't survive as a senior developer at a startup without being being able to write code under pressure. If you want someone who can glue various systems while cross communicating to various stakeholders look for someone at a larger company. If you want both, look for both sets of experience on the resume. People with 10+ will filter out positions that won't succeed at better than you can filter them out.
- greenyoda 5y ago
  > If you want good coders look for resumes with startup experience. You don't survive as a senior developer at a startup without being being able to write code under pressure. Lots of code that's written under pressure isn't good code. It's code that barely works and is hard to maintain. For a startup that's trying to get an MVP out quickly (and may not be around in a couple of years), that may be just what they need. But a huge company like Google needs developers who can write software that's reliable, performs well and is maintainable for years after the original developer is gone.
ripper1138 5y ago
I’ve seen way too many people show up after a 12 week “SWE interview bootcamp”, pass interviews, and not know how to read an API doc and write code against it. I’ll take the experienced dev.
- greggman3 5y ago
  That an interesting experience. I've never seen someone that can take a 12 week bootcamp and pass leetcode style questions. Bootcamps teach short term facts, not problem solving or at least that's my experience. I'm not saying leetcode questions are the best (no idea) but in general, someone who can generally answer them has a higher chance of being a productive developer than someone who can't and bootcamp students rarely can in my experience.

3 ms·

I’ve seen way too many “experienced devs” who are terrible coders.

by hamandcheese 5y ago

I’ve seen way too many “experienced devs” who are terrible coders.

ipaddr 5y ago
In the end prioritize for the position. If you want good coders look for resumes with startup experience. You don't survive as a senior developer at a startup without being being able to write code under pressure. If you want someone who can glue various systems while cross communicating to various stakeholders look for someone at a larger company. If you want both, look for both sets of experience on the resume. People with 10+ will filter out positions that won't succeed at better than you can filter them out.
- greenyoda 5y ago
  > If you want good coders look for resumes with startup experience. You don't survive as a senior developer at a startup without being being able to write code under pressure. Lots of code that's written under pressure isn't good code. It's code that barely works and is hard to maintain. For a startup that's trying to get an MVP out quickly (and may not be around in a couple of years), that may be just what they need. But a huge company like Google needs developers who can write software that's reliable, performs well and is maintainable for years after the original developer is gone.
ripper1138 5y ago
I’ve seen way too many people show up after a 12 week “SWE interview bootcamp”, pass interviews, and not know how to read an API doc and write code against it. I’ll take the experienced dev.
- greggman3 5y ago
  That an interesting experience. I've never seen someone that can take a 12 week bootcamp and pass leetcode style questions. Bootcamps teach short term facts, not problem solving or at least that's my experience. I'm not saying leetcode questions are the best (no idea) but in general, someone who can generally answer them has a higher chance of being a productive developer than someone who can't and bootcamp students rarely can in my experience.