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
On online collaboration and our obligations as makers of software An Essay by Baldur Bjarnason www.baldurbjarnason.com Is it the notetaking system that’s helping you think more clearly? Or is it the act of writing that forces you to clarify your thoughts? Is it the complex interlinked web of notes that helps you get new ideas? Or is it all the reading you’re doing to fill that notetaking app bucket? Is all of this notetaking work making you smarter? Or is it just indirectly forcing you into deliberate, goalless practice? Towards a crap decisionSo much knowledge not being applied notetakingbloggingsoftwarethinkingcommonplace
Towards a crap decision You have a thing. You would like to improve said thing. So, you ask a bunch of people what they think, giving more weight to those with relevant expertise. It’s a time-tested strategy. The pitfall here is that if the participants are aware of each other’s contributions, they will almost always automatically switch to consensus-building instead of providing their honest feedback. Worst case scenario: the bandwagon effect gathers steam and drives you toward a crap decision. collaborationdecisions
So much knowledge not being applied Most organisations have a lot of documents and data floating around that hardly ever gets revisited or used. They all have research, reading, and relevant information collecting dust. Stuff that should be informing the decisions and strategies of the company. Some of it sits unread in a knowledge base or a wiki. Some of it lies in the drives of individual employees who don’t have a way to share it productively. So much knowledge not being applied! Except that’s not how we work as human beings. If you haven’t read it, experienced it, and contextualised it, then it isn’t knowledge to you. Knowledge is a quality that people possess, not documents, and the only way to transfer it from one place to another is for people at both ends to apply themselves and make it their own. knowledgedocumentationwork