1:1 meetings are great - the opportunity to sit down together with someone for a time is invaluable, and something I expect managers to do with their staff on a regular basis.
But they shouldn’t just be “a thing managers do”. Whatever your role, a regular 1:1 with colleagues - whether they’re someone you work alongside every day, or someone more distant in the organisation - is an excellent investment.
I’ve acquired a bunch of Raspberry Pis over the years since they were first released in 2012, and was recently asked what I’m using them all for.
So here’s my collection of Pis in active use:
Here’s how I generally configure my GitHub repositories.
At some point I should automate this - I’m hoping that GitHub will add some cool .github/config.yaml functionality and save me some work.
Until then, this is my checklist!
Automatic dependent surveillance–broadcast (ADS–B) is a surveillance technology in which an aircraft determines its position via satellite navigation and periodically broadcasts it, enabling it to be tracked (Wikipedia)
Track aircraft with £30 of radio, £10 of antenna, plus a Raspberry Pi and assorted bits.
Courtesy of Quinn Daley, name.pn helps people get your name right, pronounce it correctly, and use your correct pronouns.
Dr. Kimberly Manning explains it fantastically:
I’ve virtually never regretted erring on the side of being more explicit about my expectations and my intents.
I like to distinguish between “distributed” and “remote”.
Being distributed is an intrinsic property - a team can be distributed, with no real central locus like an office.
Being remote is an extrinsic property - you’re remote from something, like a remote team in another country.
Your code lives in version control, with easy branching, reviewed changes, and tests, right?
Does your documentation?
By writing code in a non-standard fashion, we took on overhead that we would have not had to worry about had we stayed with the widely used platform defaults
Don’t underestimate the costs of doing your own thing.