Dung Vu @rta_dungvu@m.rthome.me
RTA (TEST)
Joined Mar 2019
"...a codebase might be “messy.” But software is most useful when it accurately models the world, and the world is decidedly messy."
https://medium.com/swlh/what-happens-when-you-lack-senior-engineering-leadership-84ce189158b2
"Ninety-nine percent of the failures come from people who have the habit of making excuses"
---
George Washington Carver
[Today Reading] GEMBA WALK - GO SEE, ASK WHY, SHOW RESPECT
> https://www.lean.org/shook/DisplayObject.cfm?o=1843
"The important point here is, that the development team does all this for their own benefit and among each other! The Daily Scrum should help them adapt their plans, so that they increase the chance to reach the Sprint Goal. For this the dev team must know how their progress is trending towards completing the work in the Sprint Backlog."
-> https://medium.com/serious-scrum/why-your-daily-scrums-suck-part-1-f77a5a38ceac
-> https://medium.com/@morgler/why-your-daily-scrums-suck-part-2-346072766bd0
Without changing our patterns of thought, we will not be able to solve the problems we created with our current patterns of thought. (Albert Einstein)
“[Younger programmers] might insist that everything is new and different nowadays, that the rules of the past are past and gone. If that is what they think, they are sadly mistaken. The rules have not changed. Despite all the new languages, and all the new frameworks, and all the paradigms, the rules are the same now as they were when Alan Turing wrote the first machine code in 1946. But one thing has changed: Back then, we didn’t know what the rules were.”
https://medium.com/decoupled/distilled-clean-architecture-a6781ca07e0a
[Today Reading] Strategies for Handling Unplanned Work During Sprint
https://medium.com/agilelab/strategies-for-handling-unplanned-work-during-sprint-2f89697509ff
Biggest design trends for 2020
https://uxdesign.cc/biggest-design-trends-for-2020-8988bf2d5caa
Figma: the collaborative interface design tool
https://www.figma.com/
https://blog.prototypr.io/goodbye-adobe-43d4fc4d6095
[Today reading] How to Write Good Error Messages
https://uxplanet.org/how-to-write-good-error-messages-858e4551cd4
https://about.gitlab.com/blog/2016/03/03/start-with-an-issue/
"Before you begin anything else, summarize your ideas in an issue and share it. It’s such a simple rule, but the impact is huge."
A system’s being “fail-safe” means not that failure is impossible or improbable, but rather that the system’s design prevents or mitigates unsafe consequences of the system’s failure. That is, if and when a “fail-safe” system “fails”, it is “safe” or at least no less safe than when it was operating correctly.
[Today reading] DESIGN THINKING - A 5 Stage Process:
https://www.interaction-design.org/literature/topics/design-thinking
"We don't need competition between people.
There is competition between every person and this mountain.
The last word always belongs to the mountain."
SOLID Principles-simple and easy explanation -> https://medium.com/better-programming/solid-principles-simple-and-easy-explanation-f57d86c47a7f
😂
> We could, for instance, begin with cleaning up our language by no longer calling a bug a bug but by calling it an error. It is much more honest because it squarely put the blame where it belongs, viz. with the programmer who made the error.
RTA (TEST)
Joined Mar 2019
