Multitudes

Multitudes

@multitudes.co

Turn your engineering metrics into a tool for continuous improvement. Along the way, get more from your AI tooling, catch AI slop early, and support AI learning. More at: www.multitudes.com

77 followers32 following54 posts

Feedback Quality v2 is live! A bunch of you told us what you loved about v1 and what we could do to make it even better, so we listened (and made changes)! Thanks for helping us reclassify feedback, and flagging when our model read too much into the use of cheeky emojis. More here: bit.ly/46fkgXn

We had a great TLC w Ian McFarland from Kard on the 7 wastes of software development – his take on Taiichi Ohno's revolutionary framework 🙌 The talk covered heaps, from how to deal w code debt to preventing over-designed systems. Full recording + materials: www.multitudes.com/blog/tech-le...

multitudes.comTech Leader Chats: How to reduce software development wastage by Ian McFarland - MultitudesMultitudes presents another episode of Tech Leader Chats: How to reduce software development wastage by Ian McFarland.

🚨 Feedback Quality is now live! We're delighted to ship v1 of this new feature, allowing you to identify what constructive feedback looks like for your team. Our model classifies your feedback, finds patterns, and gives you examples to use in coaching conversations. Learn more: bit.ly/4mTewZ9

multitudes.comFeature Launch: Improve your team’s code review processes with Feedback Quality - MultitudesMultitudes is delighted to present our Feedback Quality feature, allowing you to identify what constructive and actionable feedback looks like for your team, where rubber-stamping might be happening, ...

How this works in practice ➡️ The view shows the distinct number of calendar hours disrupted by pages. For example, if there are pages at 6.30pm, 7.15pm, and 7.25pm, we would count two disrupted hours (6-7pm, and 7-8pm). Want to see it in action? Book a product demo: multitudes.com/demo

With this new view, you’ll be able to clearly see the difference between concentrated and distributed disruptions to better understand the human impact on your team.

That’s why we’ve launched a new Disrupted Hours chart view – now you can use our in-chart toggles to view page disruptions based on the total number of pages or the distinct number of hours disrupted by pages. 🤩

Looking after your team’s wellbeing while managing on-call page disruptions can be a juggle. PagerDuty research found that 54% of page responders are being interrupted outside of normal working hours. The wellbeing impact of being paged 5 times over 5 hours is larger than 5 times in one hour.

The research discusses the perceived tension between being human-centric AND data-driven; teams want to be both but struggle with how. What helps is building trust and being transparent with the use of metrics, because those support psychological safety. 💡

📚 Our Help Center Docs have had a major uplift. 📚 They're now better organized, visually cleaner (with a dark mode option), and searchable. This makes it easier to find answers to your questions; check out the new search bar to see more (yay for cmd/ctrl+k!). Take a look 👇 docs.multitudes.com

🤔 “How do I balance technical debt alongside new feature delivery, when crafting a technical roadmap?” Join us for a #TechLeaderChat on Wed 19 Mar/Thurs 20 Mar with Vindhya Joseph, Enterprise Architect at Foodstuffs, to talk about exactly this! 🗺️ Details and RSVP here: bit.ly/TLCTechnical...

📅 Outlook Calendar integration now live: See whether meeting time is impacting your team's ability to deliver. 📅 Multitudes now integrates with Outlook Calendar to show focus time, fragmented time, and meeting load for you and your team. 👏👏 #FocusTime #OutlookCalendar #NewIntegration

With this new feature, you’ll get insights on: 🕚Focus time – how much time people are getting for deep work 🕚How much time your team is spending in meetings during the week – and how much less time they have for feature work 🕚The wellbeing impact of out-of-hours meetings

Multitudes reposted

My new iPad case got a glow up! I love green and these messages always make me happy when I see them! The back of my iPad case is PyConAu curlybois.

Multitudes@multitudes.co

Who doesn't love a good piece of merch?! Our stickers, which are our values, were an absolute hit at #PyConAU last year – especially with @jrosenbaum.com.au! #LoveMerch #Tech #Stickers #Values #FreeMerch

T-2 days until our next #TechLeaderChat – don't miss the opportunity to hear from leading researcher and AI artist, @jrosenbaum.com.au, on why gender is fundamentally misunderstood by machine learning systems 🙌 It's one not to miss! RSVP here 👇 bit.ly/AIperception...

bit.lyHow to overcome AI’s biased perceptions of gender, Thu, Jan 30, 2025, 11:00 AM | Meetup**How to overcome AI’s biased perceptions of gender** In a world where AI increasingly shapes how we see and represent ourselves, understanding how these systems interpret

Our next #TechLeaderChat is happening next week! Have you RSVP'ed yet? 🙋 J. Rosenbaum (@jrosenbaum.com.au), AI artist, researcher and lecturer, will explore why gender is fundamentally misunderstood by machine learning systems and more. RSVP now 👇 bit.ly/AIperception... #AI #GenderBiases #Tech

bit.lyHow to overcome AI’s biased perceptions of gender, Thu, Jan 30, 2025, 11:00 AM | Meetup**How to overcome AI’s biased perceptions of gender** In a world where AI increasingly shapes how we see and represent ourselves, understanding how these systems interpret

Trait #4 (2/2) - 💡 Technical ability: Sean also doesn’t think strong engineers need to be particularly hard workers with working long hours. His experience suggests that good work looks like short intense bursts of productivity separated by long periods of relative inactivity.

Trait #4 (1/2):💡 Technical ability – Deeply technical people will see simple solutions that others miss, and solve whole categories of problems that others can’t.

Trait #3: 💡 Speed – They work fast. Sean believes there are two reasons for this – they don’t put off hard work, and they tackle hard tasks which means they accumulate experience rapidly.

Trait #2:💡 Pragmatism – They get things done and have a bias towards working solutions. They're ruthless pragmatists: every design decision is judged by how well it'll work, not how clean or elegant it is. They’re typically happy to make compromises in the interest of shipping.

Trait #1:💡 Self-belief – Software problems are all unfamiliar problems, therefore engineers work in the dark. For each new piece of work, it’s impossible to say how tricky it’ll be until it’s completed. Strong engineers have the confidence to know they can figure it out.

Takeaway #3: If the wants and needs of the company and employee are not aligned, you’re not doing them any favors by dragging it out or keeping the employee around in a prolonged state of purgatory.

Takeaway #2: You should rarely try to change someone’s mind about leaving. But always try to understand why they’re leaving. Offering some form of development vs throwing money at the employee has worked for Charity.

Some of our key takeaways from the blog: Takeaway #1: Making sure the right people are on the team is the #1 job of a manager. If this requires managing people out, then figuring this out swiftly (months, not years) is critical.

Our community for Tech Leader Chats has hit 800 members! 🎉 We’re thrilled to hit this milestone, as our group continues to grow and be a place where engineering, product, and data leaders come to learn, grow, and connect.

During @web-goddess.org’s talk about creativity in the age of AI, we asked our #TechLeaderChats community questions about AI and code development. While it was a small sample size (16 webinar attendees), the data showed interesting insights:

In terms of HOW engineering teams are using AI tools, they’re primarily using them in: 1️⃣ Code generation (56%)  2️⃣ Documentation generation (20%) 3️⃣ Test case generation (13%)