Teamwork

Developers love to talk about tech debt, especially if the developer responsible for introducing it is no longer around. However, often, talk is all that happens because no one can agree on what to tackle first. Here, we look at how to overcome disagreement and get on with paying off that debt 💷.

Anyone who has ever worked in a team knows only too well that there is no one true way of formatting code. A team sits down and agrees on what is important to them. These sit-downs can be fraught with danger. Here, we look at how SwiftLint can remove some of that danger.

Coincidental duplication is where we see common functionality between features that just happen to behave or look the same but were never intended to be the same. We then take this coincidental duplication and wrongly build a coupled solution around it. Here, we look at how to avoid that.

An uncomfortable truth is that praising firefighting developers might just be leading to more fires. Here, we look at why needing firefighting developers is a sign that your processes need to be improved, as avoiding fires is better than managing fires.

Everyone has a view on how to style code. None of that matters. What matters is that, as a team, you agree on the most important styles to enable developers to feel a sense of familiarity when navigating the project, regardless of who wrote the code. Here, we look at some style rules.

People form tribes. It's such an ingrained part of human nature. Our tribe becomes part of our identity. You see this behaviour in every aspect of human society. You see it in development teams. Here, we look at how to overcome this instinct when we need to merge two development teams.

You are a great developer, so why go through the hassle of writing unit tests? Here, we look at the reasons beyond writing unit tests and how to win over a unit test sceptic

It's increasingly rare for an app to be built by one developer. With multiple developers comes the need for sharing. Here, we look at how to share an iOS certificate between different developers on your team.