|
|
|
|
|
by sedachv
2455 days ago
|
|
> Had no real way of submitting it other than emailing it to the interviewer as a zip. Being good at email (ex: not relying on GMail, knowing basic things about line length, top-posting, signature, having your own domain(s), using an actual email client instead of webmail crap, Sieve filters and mailing list management, actually knowing how mailing-list based development works and being able to use (git) patch/diff, bonus points for offline syncing, 2x bonus for using a text client (3x bonus for xmh), 10x bonus for running your own server(s)) is a way better indicator of technical competency than the ability to sign up for a GitHub account and click a few buttons. HTML email is a huge red flag for programmers. |
|
My first intuitions would be that they’re likely reluctant to make practical compromises, slow to accept norms, and that they’re prone to chasing rabbits. They might have a role on a large team or for a very specific project, but there’s be some wariness for sure.