{"id":384,"date":"2011-02-10T16:44:52","date_gmt":"2011-02-10T23:44:52","guid":{"rendered":"http:\/\/www.jacksonleung.com\/blog\/?p=384"},"modified":"2011-02-15T12:26:46","modified_gmt":"2011-02-15T19:26:46","slug":"modify-as-little-as-possible","status":"publish","type":"post","link":"http:\/\/www.jacksonleung.com\/blog\/modify-as-little-as-possible\/","title":{"rendered":"Modify as Little as Possible"},"content":{"rendered":"
\"modify<\/a>
modify as little as possible<\/figcaption><\/figure>\n

Today’s post is going to be on my opinion on modifying existing systems. Unless you’re a one-man-coder-army, and if you are… kudos, but often times, you’ll find yourself working with other people’s code. When working with code that you’re not too sure of its functionality, you should tread extremely carefully. Make small changes, review the effect, and then proceed. I’ve seen a lot of projects go wrong when they change multiple elements of a system to get to a specific result, only to fail, and then absolutely have no idea what went wrong.<\/p>\n

By making small incremental changes, you can change the direction of the project when you’re getting unexpected results, you’ll also know what went wrong, and you can also correct it quickly. That being said, you can probably feel more confident making these changes if you were in a TDD (test driven environment), since you can run a regression test on the existing system to make sure nothing is broken and everything is working the same. On the other-hand, a TDD environment introduces its overhead. Unless you have a TDD environment, it’s probably best to stick with the practice of making your changes small incremental bursts followed by a lot of review.<\/p>\n","protected":false},"excerpt":{"rendered":"

Today’s post is going to be on my opinion on modifying existing systems. Unless you’re a one-man-coder-army, and if you are… kudos, but often times, you’ll find yourself working with other people’s code. When working with code that you’re not too sure of its functionality, you should tread extremely carefully. Make small changes, review the … <\/p>\n

Continue reading “Modify as Little as Possible”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-384","post","type-post","status-publish","format-standard","hentry","category-programming","entry"],"_links":{"self":[{"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/posts\/384","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/comments?post=384"}],"version-history":[{"count":4,"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/posts\/384\/revisions"}],"predecessor-version":[{"id":395,"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/posts\/384\/revisions\/395"}],"wp:attachment":[{"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/media?parent=384"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/categories?post=384"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.jacksonleung.com\/blog\/wp-json\/wp\/v2\/tags?post=384"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}