Give clients control from day one

We join a fair number of projects each year, and it's very common to uncover a surprise where we need the previous developer to transfer something they set up on their own.

In the latest episode of the No Compromises podcast, we explain why every project should start in the client’s own GitHub organization, even when the client has never heard of git.

We share onboarding tips and war-stories that show how small shortcuts turn into big headaches later.

You’ll learn a repeatable way to protect both your reputation and your client’s project.

• 00:00 Setting up the problem
• 02:15 Quick hack versus right process
• 03:30 Project-setup technical-debt risks
• 05:00 Declaring non-negotiables to clients
• 06:45 Docs that survive “hit-by-bus” events
• 08:00 Solo-dev reputation boosters
• 08:45 Silly bit

Listen Now (11 min)

And after listening, don't forget to subscribe to the podcast, so you don't miss future episodes.

Here to help,

Joel

P.S. If you like this approach to software development, read more about how we work with clients.