
Sign up to save your podcasts
Or


Summary
Justin Mills, software engineer at Yesware tells me about their flat organizational structure and development practices.
Details
Little about Justin and Yesware; team structure, no test team, no defined team leads; no cohesive architecture; shared infrastructure, hierarchy might be needed; getting approval to reduce technical debt; assigning teams to tasks, trying open allocation, ending open allocation; no titles in engineering but other departments have titles; no one in a position to make a tough decision; struggling with agile, speed of development is the goal.
By Bryan Hogan5
55 ratings
Summary
Justin Mills, software engineer at Yesware tells me about their flat organizational structure and development practices.
Details
Little about Justin and Yesware; team structure, no test team, no defined team leads; no cohesive architecture; shared infrastructure, hierarchy might be needed; getting approval to reduce technical debt; assigning teams to tasks, trying open allocation, ending open allocation; no titles in engineering but other departments have titles; no one in a position to make a tough decision; struggling with agile, speed of development is the goal.