Rather good article: "How to Build Good Software" https://www.csc.gov.sg/articles/how-to-build-good-software …
Show this thread
-
Software is about developing knowledge more than writing code: "If a new team takes over the code for an unfamiliar piece of software, the software will soon start to degrade" because they don't have knowledge of the design choices which created itpic.twitter.com/JmiIvwZo6t
Show this thread
This why any time my team takes ownership of a repo from some other team I schedule a task for reading the code and understanding ithttps://twitter.com/qntm/status/1165010052014649344 …
-
-
(Actually, the main reason I do that is because I need to know what liabilities we're inheriting. Known bugs, incomplete features, absent coding standards, disregard for standard development practices)
Show this thread -
"[N]o amount of planning will eliminate all shortcomings" - I reach this point in planning meetings, like a phase change, when it's clearly ceased to be useful to spend more time talking, and it's time for us to leave the room and go and build somethingpic.twitter.com/Bto3cqgA2D
Show this thread -
"Overall, good engineers are so much more effective not because they produce a lot more code, but because the decisions they make save you from work you did not know could be avoided"
Show this thread -
I also like this article because of its restrained tone, citation of significant real-world projects and highly limited use of stock photos
Show this thread
End of conversation
New conversation -
-
-
Can I work for you?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.