About my time in Split, Croatia; about Schengen rules for travellers, and Uber outside of the US
What drives your daily work: your resume or your product? Unfortunately, more and more developers are only motivated by their resume rather than by their team's success. In this talk, we discuss how to empower your team to learn new skills while minimizing adverse effects of maintenance and planning costs.
Have you tried to "reinvent the wheel"? Or wanted to try that new UI framework that just came out? Many of us have, and it is often a beautiful sign of passion for our craft. Unfortunately, for some developers, this desire to use something new is only driven by their resume building.
While buzzwords like serverless, blockchain, microservices look good on the resume, they might not be a good solution for your product. Instead of trying to push a project to use new technology, developers need to find the right tools for the right problem.
In this talk, we discuss how to empower your team to learn new technologies and new skills while avoiding adverse effects like maintenance cost. We learn how to prioritize learning and to keep your team interested in the project at hand.
- Dangers of Resume Driven Development
- Tips and tricks to prototyping and learning with your product in mind
- Lessons on how keeping your team interested and excited about your product