,
4 tweets,
2 min read
Read on Twitter
I've thought about this @holman tweet at least once a week since last July.
Even when I've worked on things that are considered relatively hard (e.g., an algorithm that won best paper award at a top conf), the work hasn't been interview-style hard.
Even when I've worked on things that are considered relatively hard (e.g., an algorithm that won best paper award at a top conf), the work hasn't been interview-style hard.
To the extent that things are hard, it's been stuff like:
Your TL thinks version control and automated tests are a waste of time. How do you convince them otherwise?
Your team has 75% turnover in well under a year for... reasons. How do you stay productive?
Your TL thinks version control and automated tests are a waste of time. How do you convince them otherwise?
Your team has 75% turnover in well under a year for... reasons. How do you stay productive?
On the flip side, when I've worked with people who are unproductive, it's never been the stuff people say interviews filter for (can't program, not smart enough). It's been stuff like: we sucked at helping the person ramp up, manager or senior team member was hostile to them, etc
