Scrum is like the rules of soccer. Following them does not make you a good player.
The best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer.
In carpentry you measure twice and cut once. In software development you never measure and make cuts until you run out of time.
These days, the problem isn't how to innovate; it's how to get society to adopt the good ideas that already exist.
If you say "I told you so", you are the one who has failed. Because you knew, but did not manage to stop the train wreck.
Programmers have to fight against the two most destructive forces in the universe: entropy and stupidity.
Promoting a good developer to management is often a twofold bad move: you'll lose a good developer and get a poor manager.
Bad programmers worry about the code. Good programmers worry about data structures and their relationships.
The competent programmer is fully aware of the strictly limited size of his own skull; therefore he approaches the programming task in full humility, and among other things he avoids clever tricks like the plague.
Almost every attempt at making something better will be regarded by someone else as a personal attack.
I know testers who make good devs. I know devs who make good testers. I know Scrum Masters who make good coffee.
We crave for new sensations but soon become indifferent to them. Wonders of yesterday are today common occurrences.
Every great developer you know got there by solving problems they were unqualified to solve until they actually did it.
Start out with finding the right problem to solve. This is a combination of “what customers are asking for”, “what customers don’t even know they want yet” and “what can be solved with something simple to understand and manage”