Code review - Robert C. Martin
Which door represents your code? Which door represents your team or your company? Why are we in that room? Is this just a normal code review or have we found a stream of horrible problems shortly after going live? Are we debugging in a panic, poring over code that we thought worked? Are customers leaving in droves and managers breathing down our necks? How can we make sure we wind up behind the right door when the going gets tough? The answer is: craftsmanship.
ฝึกที่คำคมนี้
แก้ไขข้อความ
หรือเพียงแค่ให้ความคิดเห็น:
