SSW Rules
Documenting decisions and discoveries with Piers Sinclair
Work can change quickly. So, if decisions and discoveries haven’t been documented, it can cause significant pain down the line.
Read MoreMonitoring your Azure costs with Warwick Leahy
Managing the monthly spend on cloud resources (e.g. Azure) is hard. It gets harder for the Spend Master (e.g. SysAdmins) when developers add services without sending an email to aid in reconciliation.
Read MoreChecking 3rd Party Libraries before Installing with Chris Clement
Efficient software developers don’t reinvent the wheel and know the right libraries to use. Using an already existing and well-tested libraries will speed up development time.
Read MoreCatering to your audience with Piers Sinclair
Often when you are talking with others, it is easy to forget they have a different background and experience to you. Then, once you start explaining something to them, they easily become lost.
Read MoreDefining PBIs and talking to the Product Owner with Luke Cook
It is very common that a developer looks at a PBI to work on, and find out that it has limited or missing information.
Read MoreThe 5 pillars of teamwork with Ulysses Maclaren
Hear from SSW General Manager, Ulysses Maclaren, as he explains the 5 pillars of effective teamwork, based on the book by Patrick Lencioni
Read MoreEvent Storming with William Liebenberg
Do you know the value of Event Storming?
Often when building systems it isn’t super clear what all the nuts and bolts should be. There might be several major stakeholders or domain experts each with slightly different ideas understanding that causes contention in how the system functions.
Read MoreThe dangers of your strong suits
“When you have a hammer, everything looks like a nail.”
This saying is often used for developers who want to use their favourite technology to solve every coding issue, even when it’s not the best fit. But this saying is actually relevant to us all.
Read MoreDo You Know When To Ask For Help?
When you’re working, you will encounter issues that block you from progressing, and force you to do some googling, and investigation on how to move forward. These moments can be stressful, especially for junior developers and the question arises, “When should I ask for help?”
Read MoreDo you explain a problem by zooming in and out with Luke Cook
Explaining problems can be really hard. Often, when you are trying to talk with someone about it, they get lost and frustrated because they don’t fully understand the context.
Read More