- Prefer Isolating Actions than Combining
- Duplication is better than the wrong abstraction
- Don’t wrap good libraries for the sake of wrapping
- Always take a step back and look at the macro picture
- Concepts need shift in Mindset. Cannot be applied blindly like tools
- Don’t let <X>-ities go unchallenged. Clearly define and evaluate the Scenario/Story/Need/Usage.
- Refactoring is part of each and every story. No code is untouchable

medium.com/@rdsubhas/10-modern

joelonsoftware.com/2000/08/09/

12 Steps to Better Code

> A score of 12 is perfect, 11 is tolerable, but 10 or lower and you’ve got serious problems. The truth is that most software organizations are running with a score of 2 or 3, and they need serious help, because companies like Microsoft run at 12 full-time

joelonsoftware.com/2000/04/30/

Top Five (Wrong) Reasons You Don’t Have Testers

> ...If you’re in a hurry, skip the rest of this article, and go out and hire one full-time tester for every two full-time programmers on your team.

Four Ways a Product Owner can Ruin a Scrum Team
1. Lack of Focus or Vision
2. Poor Communication Around Objectives and Results
3. Lacks Ability or Authority to Define Work Items in the Backlog
4. Lack of Respect for the Team

medium.com/serious-scrum/4-way

Show more
m.rthome.me

rtHome Socials