all of them. He didn't start achieving career success until his 30s. Jack Ma didn’t see his first computer until he was 31. He started out his career as an English teacher making $15 per month. He is worth $24.2 billion today. Jack Ma, Founder of Ali Baba
student. When you are 20 to 30 years old, you should follow a good boss & join a small company to learn how to do things properly. When you are 30 to 40 years old, if you want to do something yourself, just do it. You still can afford to lose, to fail. when you're 40 to 50 years old, my suggestion is you should do things you are good at. When you are 50 to 60 years old, spend time training and developing young people, the next generation. When you are over 60 years old, spend time for yourself. Jack Ma, Founder of Ali Baba
right practices GOVERNANCE have managers with skills and experience at product management, agile & lean mindset, both commander and servant leadership models, technical background, coding & design, empathy, hard & soft skills
do is build your first 10 employees with B-level people. You will end up with 100 C-level people. That's why we hire very slowly. Steve Newcomb founder and CEO, Famo.us
developers to you, because they only want to work with the best. If you hire B-level programmers, they will recommend C-level programmers so that they'll look better by comparison. Steve Newcomb founder and CEO, Famo.us
Pull changes and merge Build and run tests again Checkin changes regularly New pull request Notify Build and run tests Deploy to CI env Run simple tests Build complete Update build status: Green! Push to upstream Review Approve Merge Build and run tests Deploy to prod-like env Run acceptance tests Build complete Notify Notify Deploy artifact to repository Notify Mark build as release candid. Resolved (Ready for client approval) developer vcs host ci server deploy server test server build ci-cd pipeline at the very beginning
a/b testing usage analytics user acceptance testing alpha / beta unit testing & tdd integration testing api compatibility via contract testing testing non-functional properties performance testing load testing security/penetration testing static code analysis checking quality attributes business facing technology/implementation facing concept defined by Brian Marick and revised by Lisa Crispin & Janet Gregory support the team pass/fail confirmation checking for expected outputs preventing defects critique the product driven by data analysis and investigation analyzing undefined, unknown and unexpected finding defects AGILE TESTING QUADRANTS manual manual& AUTOMATED AUTomated did we build the right thing? did we build it right? how can i break the system? can the system scale? diagram prepared by Lemi Orhan Ergin AUTOMATED via special tools before/while coding post coding
based development with Feature Toggling Easy refactoring with mono repo Deploy to prod even in 1st sprint Commit early, commit often, perfect later, publish once Stop calculating code coverage Delete your brittle tests, rewrite tightly coupled code Use 20% of time for eliminating technical debt Multi-level testing for minimizing the need to manual testing Build modular monoliths think different