This is a talk about how shifting the focus from craft to product has affected ustwo. Their delivery teams are required everyday to make trade offs between what would the "best" technical solution and what's right for the product they are delivering. Ultimately, they get paid to solve business and user problems, not to be perfectionists. Should the vision of a product affect your development practices? Could you be delivering perfectly valid, beautiful code that solves the wrong problem? Is there such thing as "good practices"? At ustwo they work with all sorts of clients, from startups to multinationals, giving them an amazing opportunity to see these issues from very different angles. They would like to share their experience and hear yours!
YOU MAY ALSO LIKE: