Code developing flow

In my career I fist using yahoo working flow for co-work with other developers.
The flow is basically devided responsibilities into different engineer group :

1. Developers
2. QEs
3. Release engineers

插（漫）畫家 Mark 總結：
1. 讓人停不了的事
2. 合乎人性的事（讓人更懶的事｜讓人變年輕的事）
3. 立法禁止的事

第三條讓我想到我的長輩跟我說過件事：早期韓國華僑很多都靠走私一些禁止品賺錢，現在沒這個方法了，因為正當貿易的管道都開放了～～～

立法禁止真的可以杜絕需要嗎？ 還是我們可以有更好的方式，通常禁止都是最不花力氣的方法，聰明人可以有更聰明的作法。

1. Losing 20 kg
2. Rust|exlier language
3. Master in CSS layout
4. Make at least two pull-request on ReactJS echo-system( next.js | medium-draft…etc)
5. Improve English ability like a native speaker
6. Pick on material art as long-term habbit

https://www.xuehua.us/2018/07/11/%E5%A7%9C%E6%96%87%EF%BC%9A%E6%B1%9F%E6%B9%96%E8%B7%AF%E8%BF%9C%EF%BC%8C%E6%88%91%E8%87%AA%E6%A8%AA%E5%88%80/zh-tw/

寫個人 寫成了江湖～

While using docker multi-stage building
it will produce several intermediate images often with very big sizes and named: <none>, which makes products a little dirty.