Organize things around your perks, don’t fight them
Don't aim to get a senior software architect unless you are ready to deal with several technological stacks at the same time, write stupid product specs and write no code for months. Know what you want - it is ok to change your goals.
Compromises are only useful if it is one-time and on the right spot. Otherwise you rob them from the precious resource for improvement - the bad example.
Пример с Пресли/Траян и как естимейтите те карат да помислиш
Code Style saved a lot of GIT log review time * Refactoring is natural * Refactoring clarity
Примера от по-горе с кухнята
Working the right way, by knowing all the wrong ways
Working the right
way, by knowing all
the wrong ways
■ JIRA is for tasks, not for showing off how good you are!
■ IDE vs Editor - Noone cares
■ How quickly do you do code refactoring?
■ Are you so proud that you know the project by heart?
■ Don’t remember! Recreate!
Know your tools
"Premature optimization is
the root of all evil."
Walk in the QA shoes
● The fact that there is a separate QA team, indicates that
"you don't care", leading you away from craftsmanship.
● QA team just helps you with an extra POV
● Some companies deliver to production within the
working day ?!?!?!