(no title)
Novashi | 7 years ago
Toxic and off putting. You put too much weight on relatively minor things. It’s preventing you from fairly considering the rest of the candidate. You could be the one to teach them to do READMEs well.
Novashi | 7 years ago
Toxic and off putting. You put too much weight on relatively minor things. It’s preventing you from fairly considering the rest of the candidate. You could be the one to teach them to do READMEs well.
beardedwizard|7 years ago
chillacy|7 years ago
unknown|7 years ago
[deleted]
zepolen|7 years ago
1. A developer who doesn't respect himself first and foremost to write a README/maintainable code so that his future self and others can have an easier time.
2. A developer who cares about communicating his work to himself/others and making the environment easier for everyone to work for the future.
Right.
Novashi|7 years ago
Developers are at various stages in their expertise when they go looking for jobs. READMEs are nice but try not to let yourself get tied up with emphasis on a few signals that document the whole human. README quality is a pretty weak signal.
If you bring up the README in an interview, and the dev cannot find any motivation or acknowledge that it could be better, then maybe you might have to pass on them. My problem with your methods is that you get to this point without even opening a discussion.
READMEs are a relatively teach-able skill and in pretty quick fashion. Maintainable code, much less so obviously.
chickenfries|7 years ago
amitport|7 years ago
Anything beyond that is unfounded bias IMHO.
(I have a lot of personal projects and I've conducted interviews)
beardedwizard|7 years ago
bjourne|7 years ago