2018/07/12 MidsTest with Rob Lambert

This month’s MidsTest Meetup was with Rob Lambert, talking about “How to Thrive”

He met a person at a conference who was incredibly angry at everyone, his role, his company, and testers. Rob didn’t want to be like that. This combined with the birth of his child, he wanted to make the best of himself, and made a plan of what he wanted to do with himself, and so made a list of what he wanted to do.

In his talk he goes over 10 ideas to thrive.


The time is now!

There can be a worry that the industry is in turmoil and it’s a bad time to get into the industry. But there is always things going on, so it’s never worth holding back.

Have fun with it

If you’re unhappy doing something 7 hours a day, 5 days a week, 52 weeks a year, that it too much of your time unhappy.

Decide to thrive

You need to decide to thrive, it isn’t your employer’s responsibility to improve you.

Trade your freedoms wisely

You have to trade your freedoms wisely. You need to find the environment where you will thrive.

Ship software

If you don’t ship, your customers don’t get value. A testers role isn’t to stop things, it’s to help things released.

Embrace our differences

Rob explained the Disc profile

Dominating – People you want in charge of your organisation
Influencers – People who like moving around a lot, speakers
Steadies – Bring harmony and consensus to the team
Conscientious – Like rules and code, and start doing the task

In agile we bring these types together and they clash.

D and I are assertive.
C and S are passive.
I and S are people focused.
D and C are task focused.

To get people to embrace differences, understand your strengths, so you can model yourself on your career, know your DISC, and what makes you happy. Combine that and people thrive.

Learn from our mistakes

Mistakes are an opportunity to learn. If your make a mistake, learn from it and it doesn’t keep happening.

Learn anything that interests you

Combine these two things to learn – Task based and knowledge based. Tasked based would be picking up an instrument and giving it a go. Knowledge based would be reading a book.

Forcing people to learn things they don’t want to won’t work, as it doesn’t fit their learning model.

Step outside your job description

What people do every day is the culture of your organisation. Very rarely related to technical ability. But almost every problem happens between job roles, in handoffs, not what is in your job description. If you only do your job description, you are 100% replaceable.

Ask questions

A tester’s role is entirely about asking questions. Ask them early, so problems can be avoided before code gets written.

For your career, ask if you are happy, am I getting better, have I learned from this?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s