#33 Justin Mills, Yesware


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.
**extended interview** SDLC, frequent releases probably break often,
Justin's hopes for the company's future.

Extended Interview

#32 Eliot Knudsen, Tamr and a Brave New World of Data


Summary
Eliot Knudsen, field engineer at Tamr talks to me about their machine learning tool and a new way of examining data.

Details
Who he is and what he does; what is Tamr; working with data sources, the traditional way, the Tamr way, machine learning combined with human guidance;data quality and foreign languages; Thompson Reuters example, curating data, increasing speed; deploying Tamr; how Tamr works, db, java, web client; competitors; future work