Sponge Bob Test Pants

I'm not a huge fan of triangles or pyramids but there is an interesting relationship between test levels, understanding the impact of a problem and understanding the cause of the problem. #testing

@editingemily Enjoy... Hope you headed West🙂

Ireland’s OK.

Check out our new episode of the Testing Minutes podcast, where we, with @al8xr and @RobMeaney, talked about Testability. This one is awesome. And thanks, Rob, for joining us! youtu.be/tQV7raH031I?si… #qa #podcast #testability

@joe_jag Well it's Cork like🤣

The only way I could’ve enjoyed that cup final more is if I was in Cork

By understanding this simple model, tech professionals can strategically advance their careers and understand where they need to invest their efforts at each stage.

4. Inspiration: In leadership positions, your role is to inspire. ✨ Motivate your team to strive for excellence and foster a culture of continuous improvement. Basically, be the Yoda of your tech team—wise, motivating, and occasionally speaking in riddles.

3. Influence: At the senior level, influence becomes key. 👥 Use your experience to mentor others and shape the team's direction. Think of yourself as the team's GPS, guiding them when they’re lost and rerouting when necessary.

2. Impact: As you move to mid-level, the focus shifts to impact. 💪 Apply your skills to deliver tangible results and drive value for your team. It's your time to shine like the postal worker who always delivers!

1. Interest: At the junior level, it’s all about showing interest. 🌱 Demonstrate your curiosity and enthusiasm by constantly learning and seeking feedback. Think of yourself as a sponge—no, not the one in your kitchen sink—the one soaking up knowledge!

I coach people at various stages of their careers. A simple model that I find myself sharing is The 4 I's of Tech Career Progression. I created it to help people navigate the next stage in their tech careers. Each stage builds upon the previous one:

@fergalrte My Mom speaks very fondly of your Eileen @fergalrte, thoughts are with you from the Meaneys out in Douglas.

We lost our mum last night. Eileen at 92. Widowed at 42 with 6 children, youngest just 5. With love and determination she got us through those traumatic times. A stay at home mum until then she forged a career and ran businesses. A great lover of and beloved by all small children

@heather_reiduff @AgileTD Mostly conscious 🤣

@AgileTD @RobMeaney conscious leadership right up your street

The #AgileTD #CallforPapers closes on Feb 11! 🙌 Get your brain set, and prepare a paper for one of these hot topics: AI & Robotics in Testing, Machine Learning, Ethics in Tech, Conscious Leadership, Sustainability Testing, and Accessibility Testing. ➡️ bit.ly/3Gt1Ync

@t15k Mobile or embedded? We do OTAs for mobile.

@RobMeaney Easy for web apps.... but how about on device Apps?

If there was only one question I could ask when coaching teams in terms of software delivery it would be: "How could we make this change smaller and safer?" IME as teams get better at making their changes smaller and safer their performance skyrockets.

@sKriemhild I'm a big fan of continuous Integration/trunk based development meaning that we merge to trunk at least once but ideally many times a day 🙂.

And then you have teams deciding for long living branches, so everyone will have a big BANG with the update happening… twice a year (speed so far)

#AgileMaxim 1: It is in the doing of the work that we discover the work that we must do. Doing exposes reality.

Our customers want a product that makes them successful not busy teams. Stop fixating on being busy, start fixating on making customers successful.

Firstly we need we need to see results, then we can optimise for experience. Why not both? Because trying to do both means there are too many assumptions baked in and it slows the feedback loop.

My approach to software product delivery revolves around discovering the least amount of work we need to do to: 1. Validate & understand the problem. 2. Solve the problem. 3. Delight the customer. Often we have to iterate through step 1 many times before we get to step 2.

In software product development we should optimise or eliminate what we have unless there's hugely compelling evidence as to why we should add something new. 80-90% of all ideas are SHIT.. treat every new feature suggestion with enormous scepticism.

@leonardoro_ Smaller changes mean smaller cognitive load, smaller PRs, less testing etc. a catalytic probe in complexity theory talk :)