Joel and Aaron explain why every project should start in the client’s own GitHub organization—even when the client has never heard of Git. They share scripts, onboarding tips, and war-stories that show how small setup shortcuts turn into big headaches later. You’ll learn a repeatable way to protect both your reputation and your client’s code base.
- (00:00) - Intro & episode setup
- (01:15) - Create the repo in their org
- (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
Want to
level up your skills as a Laravel developer?
Episode 130
