Questions to ask on a new job search An Article by Sally Lait sallylait.com The role and expectations What does this job entail? What's driving the hire? What are the biggest challenges? What scope is there to do x, y, z? How/when/why would you consider hiring me to be successful? What does progression from here look like? What's the biggest mistake I could make? The wider business Can you tell me a bit about the company? What about the culture? How does diversity, equity, and inclusion play into this? What's the most exciting thing on the company horizon? What's been the impact of COVID-19 on company finances/strategy? What are the best and worst things about working here? Day to day What's the size/structure of the team I'd be around/have reporting to me? Which other people would I work most closely with? What technologies/tools would I work with? What could I do that would make your life easier? The practical bits What salary are you offering for this role? Additional package/benefits How do you approach distributed working, and is there scope for this? What timescales are you hoping for? Holiday Job title Give yourself an extra shot: Is there anything I've said today that makes you hesitate? work
Deadlines are bullshit An Article contrariantruth.substack.com In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil. External vs. internal deadlinesWhy are internal deadlines evil?Engineers who love their work Hofstadter's LawThe Thing-deadline calculusNever enough timeDriving engineers to an arbitrary date is a value destroying mistake bureaucracysoftwareprocesswork
External vs. internal deadlines When are deadlines necessary? Contractual obligations Technical liabilities (e.g., dependency EOL) Compliance, government, investors, and other external stakeholders What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external. When are deadlines evil? Your manager says you have a deadline Your software development methodology says you have deadlines What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil? Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate. Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take. Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team. Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features. High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress. High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive. Building is never a straight line