Skip to main content
added 29 characters in body
Source Link
Joe Strazzere
  • 386.9k
  • 188
  • 1.1k
  • 1.5k

I'm leaning towards QA, as i think it would provide me more opportunities to see what decent code actually looks like, which transitions into really any field in comp sci quite nicely.

If that is your goal, you'll need to dig in on the QA processes in your target companies. Ask specifically their involvement with code.

I worked in QA for 25 years. I've never worked for a company where QA interns saw any significant amounts of code at all. Even the most senior QAers didn't see lots of code. And trust me, the code we did see often wasn't the best.

I often had aspiring developers work for me as QA interns. They learned a lot of valuable things for their future Dev careers - but "seeing what decent code actually looks like" wasn't one of them.

I strongly suspect a Development internship would prove more valuable. You'll obviously get to see at least some code in that role.

I'm leaning towards QA, as i think it would provide me more opportunities to see what decent code actually looks like, which transitions into really any field in comp sci quite nicely.

If that is your goal, you'll need to dig in on the QA processes in your target companies. Ask specifically their involvement with code.

I've never worked for a company where QA interns saw any significant amounts of code at all.

I strongly suspect a Development internship would prove more valuable. You'll obviously get to see at least some code in that role.

I'm leaning towards QA, as i think it would provide me more opportunities to see what decent code actually looks like, which transitions into really any field in comp sci quite nicely.

If that is your goal, you'll need to dig in on the QA processes in your target companies. Ask specifically their involvement with code.

I worked in QA for 25 years. I've never worked for a company where QA interns saw any significant amounts of code at all. Even the most senior QAers didn't see lots of code. And trust me, the code we did see often wasn't the best.

I often had aspiring developers work for me as QA interns. They learned a lot of valuable things for their future Dev careers - but "seeing what decent code actually looks like" wasn't one of them.

I strongly suspect a Development internship would prove more valuable. You'll obviously get to see at least some code in that role.

Source Link
Joe Strazzere
  • 386.9k
  • 188
  • 1.1k
  • 1.5k

I'm leaning towards QA, as i think it would provide me more opportunities to see what decent code actually looks like, which transitions into really any field in comp sci quite nicely.

If that is your goal, you'll need to dig in on the QA processes in your target companies. Ask specifically their involvement with code.

I've never worked for a company where QA interns saw any significant amounts of code at all.

I strongly suspect a Development internship would prove more valuable. You'll obviously get to see at least some code in that role.