3 ms·

I wrote a blog post on a similar topic, after mentoring several would-be engineers that were curious about finding a good fit after graduating: http://blog.pame

I wrote a blog post on a similar topic, after mentoring several would-be engineers that were curious about finding a good fit after graduating: http://blog.pamelafox.org/2013/07/what-to-look-for-in-software.html http://blog.pamelafox.org/2013/07/what-to-look-for-in-softwa... That post also turned into a slide deck: https://speakerdeck.com/pamelafox/engineering-culture https://speakerdeck.com/pamelafox/engineering-culture I think we cover very similar areas. One of the big red flags for me, personally, is code review (lack thereof). If a company doesn't believe in its value, that reflects on its whole perception of coding as a collaborative process, and I just can't get on board with them.

reledi 13y ago
That's a valuable slide deck, thanks for sharing. I'm about to join a small company that doesn't have many good engineering processes in place yet (code review being one of them). It's a big red flag for me too, but I also saw it as a challenge and an opportunity to improve how things are done there. I have experience with some of these processes because of the open source development that I've done, and that's one reason why the lead dev wanted to hire me. Hopefully I can make a positive difference in their engineering culture! Would love to hear advice from anyone who's been in a similar situation.
EdwardDiego 13y ago
What about pair programming in lieu of code review? Still a red flag?