> So called "best practices" are contextual and not broadly applicable. Blindly following them makes you an idiot.
Very true. "Best practice" are most often just "common practices" - how we've done things here forever.
That's great for standardization. It gets annoying when each team member does things their own way.
But it's a stretch to call them best. The research into what is truly best, A/B tests of various methods, or building prototypes of new experimental frameworks is rarely scheduled in sprint plans. It's actually some crazy programmers who try out these experiments in their off time based on their experience with the actual problems, which leads to truly innovative things.
Very true. "Best practice" are most often just "common practices" - how we've done things here forever.
That's great for standardization. It gets annoying when each team member does things their own way.
But it's a stretch to call them best. The research into what is truly best, A/B tests of various methods, or building prototypes of new experimental frameworks is rarely scheduled in sprint plans. It's actually some crazy programmers who try out these experiments in their off time based on their experience with the actual problems, which leads to truly innovative things.