profile

Hi, Iā€™m a creator

šŸ„§ Pie-Mail - the need for speed šŸ„§

Published over 2 years agoĀ ā€¢Ā 4 min read

ā€‹

Hi everybody! Time for your somewhat regular pie-mail!

ā€‹

Thank you so much to everyone who donated to my Movember campaign - it's really appreciated!

There's still time to donate if you feel inspired - it's a good cause. It would be great if we could tip it over $350 before the month is out!

Aside from moustache antics, it's been a meeting heavy week. All important meetings, but, meetings - especially over video call - can be pretty draining.

ā€‹

I'm glad to be able to take a break from it for a bit, to put this newsletter together - so - I hope you like it! I've also played with the format again, let me know if you have any feedback!

ā€‹


šŸƒ It's a marathon, not a sprint šŸƒ

One of the themes for my team this week has been "how do we go faster?"

ā€‹

ā€‹

Let's talk about something I love - running!

In 2018 I ran my first (and only) ultramarathon.

My goal for this race was just to get to the finish line. Which I did, even though it took more than thirteen hours!

That meant - making sure I had enough food and water. It meant taking breaks. It meant having a plan for the journey and knowing where the big climbs were. It meant walking the difficult parts, being careful not to injure myself.

ā€‹

In other words, I had to make sure my pace was sustainable.

ā€‹

I think there's a lot of parallels between this and the way we build software. It's tempting when we hear "go faster" to interpret that as write more code, work extra hours, and cut corners (like code reviews and tests) to get more things out the door.

But, this isn't sustainable. Eventually, the cut corners come back to haunt you, and the engineers burn out. It's like not making it to the finish line, because you expended all your energy too early.

ā€‹

Of course, sometimes the goal is not just to finish the race! We have pressure to get features in front of customers, make profits, and beat the competition.

With this in mind, I've been thinking about the person that came first in my race. My goal was to finish, theirs was to win.

But they wouldn't have won by just "going faster". Of course, they did go faster, but this is the result of - better training, better preparedness, more experience.

To me, that means that as much energy needs to go in to learning and getting new skills, and preparation, as it does to execution.

ā€‹

Two week 'sprints' are pretty common in software development. But software projects are much more like a marathon than a series of sprints - it's important to keep prepare well, keep moving at a sustainable pace, with the end goal in mind.

ā€‹

So we want to go faster - but what's important is that we're faster in the long term, not the short term, and that speed is sustainable!

ā€‹


šŸ“– Read

External auditors - arrogant beyond their competence:

James Christie is one of my favourite writers on misadventures in auditing. He has a wealth of experience. In this article, he shares some quick horror stories about the pitfalls of external auditors. It's worth checking out some of his writings on the Fujitsu/Post Office scandal from the UK too - really interesting and thoughtful commentary.

ā€‹

How do you actually prevent bugs?

When I'm coaching testers, one question that comes up a lot is this: "We want to test early in the development cycle - but how do we actually do that?" Here Nicola Lindgren offers up at least one really good answer to this question.

ā€‹

A simple rule for product decision making:

ā€‹This post from Adam Knight was my favourite read of the week. It again ties in to not just going fast, but making things better as you go, or as he puts it, "Don't pass up an opportunity to progress to where you want to be long term".

ā€‹


šŸŽ§ Listen

Pushpay - Founders, CEOs and Product Management:

The final part of the Six-Four interview with the early leaders at Pushpay.

I promise, I'm not sponsored by Six-Four or anything, I've just really enjoyed this series. This time they talk about something I find really interesting - making product decisions, when there are competing priorities, and dealing with a CEO/founder in the mix too.

ā€‹


šŸ“ŗ Watch

We scare because we care:

I linked this event last time, here's the recording if you missed it. Maaike Brinkhof on her journey into DevOps, and how it changed the way she tested. It was worth getting up at 5am for, but there's a recording now, so you don't have to.

ā€‹


šŸŽ® Play

LinkedIn - the game:

Can you win at LinkedIn?

ā€‹


šŸŽŸļø Events coming up

I think all dates are in NZT btw

ā€‹

Green coding, and Recovering from Mistakes (Mon, Nov 29) (that's TONIGHT):

This month Xero talks features two speakers - First up, Annie Freeman, on mitigating climate change as an engineer. Then, John Bowker, on mistakes he's made as a Product Manager (and how he's recovered).

ā€‹

Fast Forward - A Virtual Open House (Tues, Nov 30):

This one is for jobseekers, but not just for jobseekers. Four of NZ's most exciting up and coming companies are opening their doors to you, virtually. Join the teams from Imagr, FirstAML, Kami and Narrative to find out more about them, what they do, and how they do it.

ā€‹

Workshop - Building and Testing a RESTful API (Thu, Dec 2):

Josh Grant and Ministry of testing present this FREE 99 minute workshop. I like that this is build AND test - a really good way to learn about APIs and how to test them, is to build one!

ā€‹

Sunshine for Jobseekers, Monsoon for Recruiters (Thu, Dec 2):

Ministry of Testing Auckland hears from two recruitment experts - Molly Workman from RUSH, and Ryan Humphrey from Serko. They'll be giving their views on the job market at the moment, the challenges and opportunities it brings, and what it means for you!

ā€‹

Lightning talks with Countdown UX (Fri, Dec 3):

UX Auckland present Alex Smith, Bliss Ng, Michael Turley and Shira Natovich Ashkenazi from Countdown UX. They'll be sharing some learnings and reflections from this year - and for a company like Countdown, I'll bet it's been an interesting year!

ā€‹


šŸ‘‹ Thanks for reading! šŸ‘‹

I really appreciate the time you've taken to read this, and I hope you've found it useful.

Feedback always welcome, or if you just have something interesting to share - please reach out.

Take care, and reach out to me any time on LinkedIn or Twitter.

Cheers,

James a.k.a. JPie šŸ„§

ā€‹https://jpie.nzā€‹

Hi, Iā€™m a creator

Read more from Hi, Iā€™m a creator

Hi all! It's flooding and cyclones here in NZ, especially those in Auckland. I hope this email finds you safe - if you're being affected by bad weather, please stay inside until this all blows over! šŸ¤ COLAB Before we get too deep into it, I'd like to give a small shout out to COLAB. I had the chance to take part in COLABs Equitable Product cohort last year. It's eight weeks of conversation and learning with like talented peers; covering subjects like data ethics, accessibility, inclusion and...

about 1 year agoĀ ā€¢Ā 4 min read

Well hello there! Happy new year everybody. I hope you all had a good break, and are well rested heading in to the new year. I've had a good long time off, getting some rest after a busy 2022. I've found myself really eager to get back to work though, I'm looking forward to what 2023 will bring - I hope you are too! šŸ™‹ā™€ļø The value of dedicated testers In my last email, I wrote about the importance of engineers testing their work (and not just leaving it for testers). But this leaves an...

about 1 year agoĀ ā€¢Ā 4 min read

Welp, the end of the year is upon us! It's been a long and busy one. It's definitely been fun, but I'm ready for a break! I've had some interesting conversations over the last couple of weeks about quality, and the lines of responsibility - so - that's the subject of today's email. Enjoy, and see you in the new year! šŸ’» Programmers and Engineers My first job was in a busy office. Our office constantly seemed to have a dirty kitchen - a pretty common office problem. Instead of rinsing their...

over 1 year agoĀ ā€¢Ā 3 min read
Share this post