▓▓░░░░░░░░░░░░░ 10%

To start shedding unattainable software standards, let's: 🛑 Stop thinking of software as homogeneously represented by a small number of unrepresentative companies 🗯 Start being more honest about "real software process" 🛠 Demand more solutions to the real problems!! end/

🔗 I wrote about this on my blog:

🤝 Force one-to-ones: Engineers should know and be known, especially when you're building tools for internal teams. Give warm intros between new starters and as many other people in the business as possible.

2️⃣ Have many lists: We have three lists: software, people, and process. The things you need to download & sign up for, the people you need to meet, and the engineering process for shipping code. These all work in different time frames. Have many lists.

✅ Read from a script: My memory is terrible. Have a step-by-step list of things that need to get done. Start at the top and go down.

🧑‍💻 Do it in person: We're a hybrid remote team, but the onboarding process is done in person. Set the expectation that you're there to fix their problems on day 0.

☃️ Cook from chilled not frozen: Keep talking to your candidates between job offer and their start date. Before they turn up, give them a warm intro to the rest of the team.

Here's six things we do to onboard new software engineers @oxwash, a🧵

Double vaxxed, babyyyy 💉💉 24 hours of a weirdly sore arm and neck (not cool) and now at least months of protection against catching and spreading covid (very cool). It literally could not have been any safer, free-r, or easier.

I’m so excited that all these people think free travel is a human right, it’ll be great to have so many supporters behind safer, more humane immigration and refugee policies. You know, once Covid is done.

Last week - I get a brand new road bike 09:40 - I get the first dose of my Pfizer vaccine 20:40 - I clear my fastest time for a lap of Richmond Park on a bike by 20% 8 weeks time - I am invited to the Olympics (probably?)

Normalise taking your laundry to work

When building, how do you decide what problems to fix first? - Easy vs hard, - Convential vs novel - Specific vs general I find it v. easy to focus on easy common expected things (landing page, mailing list) but never the problem-specific difficult new things #buildinpulbic

One of my favourite articles about the web I've read in the last month. "Convenience can be a trap. So with this in mind, I think the web needs less fancy and more brutalism."

🙅‍♀️🛠️Deciding what not to build feels less exciting I was going to build an extra set of flashcards (static PDF) and charge money for them. I don't want to be a flashcard company (or a company that makes software for making flashcards) I don't even have a printer. #buildinpublic

Using @figmadesign to hand-craft fifty A5-size flashcards for the most common verbs 🇫🇷 ↔️ 🇬🇧 It's a fine experience, but I'll be checking out Playwright or Puppeteer soon 👀 #buildinpublic

“Do things that don’t scale” is great advise but you have to unlearn the “I bet I could automate this” instinct that LITERALLY MADE ME A SOFTWARE ENGINEER.

“Nah no, I reckon he asked about maths, not dessert” Siri failing to understand me and my priorities at a fundamental level It’s « tarte » btw

“If I have one lesson to give... it was consistency of balancing 50/50 product and marketing... you can see the point where I start doing that the [revenue] line go up... it’s just all going up because I’m building new things and I’m telling people” @yongfook @IndieHackers