Collection for Y2016W45 (2016-11-07 Mon 00:00:00 +0800 ~ 2016-11-14 Mon 00:00:00 +0800)

interview

javascript

math

opensource

programmer

programming

  • Pre-merge Code Reviews
    • 三年前的文章,但還是很值得閱讀。
    • 主要在講述作者自己平常在團隊開發時,把某個 branch merge 到 master branch 之前的 code review 遵循的一些規則。
    • 篇幅不長,條列式列出重點及其原因。
    • 節錄一下最重要的規則部份:
  1. Never Push to Master
    • Always push to a separate branch per logical unit (story, feature, bug, optimisation, refactor, improvement). Branches are easy to make and easy to merge when you use git (and you apply some of tips further down in this post).
  2. Never Merge Your Own Branch
    • This helps to ensures that code is in fact reviewed. If you are caught merging into master, you will order pizza for the whole team.
  3. Review Work in Progress First
    • When you are finished with a task, you notify the other team members that your work is ready for final review. Then you review existing branches. Before picking up a new task, you look at all open pull requests (including unfinished ones) and review the changes since the last time you checked.
  4. Merge responsibly
    • Merging a pull request is the responsibility of the whole team. A pull request can not be merged when someone in the team does not understand the code or the reasoning, or does not agree with the solution.
      (Note that these rules are starting points. Figure out what works in your team, adapt continuously.)

python

$ httpstat blog.m157q.tw/get  
Connected to 104.18.38.201:80 from 192.168.43.139:44650  

HTTP/1.1 301 Moved Permanently  
Date: Sat, 26 Nov 2016 01:01:00 GMT  
Transfer-Encoding: chunked  
Connection: keep-alive  
Set-Cookie: __cfduid=d090501284dc193137b69492e0e58d8801480122059; expires=Sun, 26-Nov-17 01:00:59 GMT; path=/; domain=.m157q.tw; HttpOnly  
Location: https://blog.m157q.tw/get  
Server: cloudflare-nginx  
CF-RAY: 3079681ae007538a-LAX  

Body stored in: /tmp/tmpn6p4a94e  

  DNS Lookup   TCP Connection   Server Processing   Content Transfer  
[    253ms   |      365ms     |       324ms       |        0ms       ]  
             |                |                   |                  |  
    namelookup:253ms          |                   |                  |  
                        connect:618ms             |                  |  
                                      starttransfer:942ms            |  
                                                                 total:942ms  

django

security

vim

  • 閒聊:使用 Vim 編輯器的第五年
    • 想想自己從高一第一次用 Vim 到現在,好像也過了 8 年了...
    • 但其實一直沒有什麼時間去刻意提升自己使用 Vim 的效率,也沒寫過 Vim Plugin
    • 從一開始抄 xatier 跟凍仁翔的 vimrc 來用
    • 到大一下開始用 Vundle 裝了些 plugin 來用
    • 到大學畢業後又重新整理一次自己真正需要用到的 Vim plugin 和一併整理 vimrc
    • 很多更快捷的按法其實我都沒有真的拿來用
    • 也許哪天會突然想卯起來研究一下吧

taiwan

skating

news

joke

misc

  • 迷思一、一定是因為營養不好,沒有體力,病才不會好!

    • 這是非常常見的觀念,然而,對於末期病人而言,他們體力的衰弱往往都來自於本身的疾病逐漸惡化,如癌症、糖尿病、腎衰竭等等。再多的營養進去,其實身體也無法吸收。甚至反而太多營養和水分會造成身體多餘的負擔,產生全身水腫、腹水等等,使得病患更不舒服。
  • 迷思二、沒有放鼻胃管,病人會因為沒有進食提早走掉

    • 國外的研究已經有證實,有沒有放置鼻胃管和生命的長短其實沒有必然的關係,反而我們應該更注重的是病人自己的選擇和生活的品質。
  • 迷思三、鼻胃管是除了經口進食以外最好的營養給予方式

    • 還有另一種更不會讓病患感到不舒服的方式:胃造口,也是在胃部置放一條管子直接灌食,這個方式不僅會比較舒適,同時在照顧上也比較方便,但是因為一般民眾仍覺得這樣的方法比較具侵入性,所以通常抱持著排斥的態度。
  • 其實,鼻胃管是一個很棒的發明,讓暫時無法由口進食的病人(如外科病人)能夠短暫地借助管子持續得到營養。畢竟,由腸胃道吸收營養,依然是比較優先的選擇。只是很多時候,它可能被濫用了。

Share


Donation

如果覺得這篇文章對你有幫助, 除了留言讓我知道外, 或許也可以考慮請我喝杯咖啡, 不論金額多寡我都會非常感激且能鼓勵我繼續寫出對你有幫助的文章。

If this blog post happens to be helpful to you, besides of leaving a reply, you may consider buy me a cup of coffee to support me. It would help me write more articles helpful to you in the future and I would really appreciate it.


Related Posts