一個週末寫TensorFlow或可以救火幾百次的。那是神人，我們凡人作不到，也不適合我們參考。
我記得 "Mythical man month"有提到，一個專業程式師一天平均寫10行程式。
那如何有效率利用這短短的幾行程式才是重點。
那如何成為有效率的0.1x工程師？
https://benjiweber.co.uk/blog/2016/01/25/why-i-strive-to-be-a-0-1x-engineer/
https://tinyurl.com/y62xeak3
這篇很好可以看看
最重點
Let’s not build that feature.
( Is there existing software that could be used instead?)
Let’s not add this functionality.
( Does the complexity it will introduce really justify its existence?)
Let’s not build that product yet.
( Can we first do some small things to test the assumption that it will be
valuable?)
Let’s not build/deploy that development tool.
( Can we adjust our process or practices instead to make it unnecessary?)
Let’s not adopt this new technology.
( Can we achieve the same thing with a technology that the team is already
using and familiar with? “The best tool for the job” is a very dangerous
phrase.)
Let’s not keep maintaining this feature.
( What is blocking us from deleting this code?)
Let’s not automate this.
( Can we find a way to not need to do it all?)
一個凡人能寫的文件，程式都有限，如何取捨是我們需要好好考慮與學習的。