Devshop Stories #2 - The Story of Why You Hire a Dev Shop

TO THE GOOD STUFF

Devshop Stories #2 - The Story of Why You Hire a Dev Shop

Josh and Tanner explain that if a project has no structure or communication, it can be difficult to complete successfully

Listen on Apple

Listen on Spotify

Listen on YouTube

Josh and Tanner explain that if a project has no structure or communication, it can be difficult to complete successfully. They tell the story of a client who originally worked with a different development company but switched to RedSky Engineering partway through the project timeline. The original company didn't communicate the project timeline, features were missing, and the overall product was unfinished. Josh and Tanner go over their process and what they do to avoid this error. They say that it’s important to have a clear understanding of what the client wants before starting work on a project. They also recommend setting up regular check-ins and communication channels so that everyone is on the same page.

Also Check Out

DevShop Stories #7 - Developer House of Horror Stories Pt. 1

In this special edition of Dev Shop Stories, Josh and Tanner discuss the shocking horror stories that they have seen in their careers. They recount tales of other developers, both experienced and inexperienced, who ended up causing issues in their software.

107 Web Design Hashtags (and Counting!)

Find the perfect hashtag from our growing list of web design hashtags. Related hashtags are grouped together so they're easier to find.

DevShop Stories #6 - The Story of How We Do Our Processes

Why are processes important? We discuss all the technologies we employ to track, manage, and develop throughout this episode. The justifications for using these particular tools and recommendations to improve client relations. We talk about why it is crucial to hold regular meetings with the product