Dung Vu @rta_dungvu@m.rthome.me

Minimum Viable Product (MVP) and Design - Balancing Risk to Gain Reward

https://www.interaction-design.org/literature/article/minimum-viable-product-mvp-and-design-balancing-risk-to-gain-reward

Outcome Variables

- 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

https://medium.com/@rdsubhas/10-modern-software-engineering-mistakes-bc67fbef4fc8

https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/

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

https://www.joelonsoftware.com/2000/04/30/top-five-wrong-reasons-you-dont-have-testers/

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.

https://blog.trello.com/more-meaningful-meetings

Manager's Guide To More Meaningful Meetings

@rta_dungvu

Chess activity at RTA

Chess activity at RTA

Today reading - What Having a “Growth Mindset” Actually Means

https://hbr.org/2016/01/what-having-a-growth-mindset-actually-means