{"id":1150,"date":"2009-01-29T01:47:33","date_gmt":"2009-01-29T09:47:33","guid":{"rendered":"http:\/\/cephas.net\/blog\/2009\/01\/29\/links-1-28-2009\/"},"modified":"2009-01-29T01:47:33","modified_gmt":"2009-01-29T09:47:33","slug":"links-1-28-2009","status":"publish","type":"post","link":"https:\/\/cephas.net\/blog\/2009\/01\/29\/links-1-28-2009\/","title":{"rendered":"Links: 1-28-2009"},"content":{"rendered":"<ul>\n<li><a href=\"http:\/\/blogs.msdn.com\/ericlippert\/archive\/2009\/01\/16\/future-proofing-a-design.aspx\">Fabulous Adventures In Coding : Future-Proofing A Design<\/a><br \/>      Quote: Premature generality is expensive. Designing code to be future-proof without a clear understanding of what the future holds often leads to excess generality; generality has very real costs, and they might be higher than the benefit accrued.<br \/>    (categories:  <a href=\"http:\/\/del.icio.us\/ajohnson1200\/software\">software<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/programming\">programming<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/architecture\">architecture<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/change\">change<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/future-proofing\">future-proofing<\/a> )\n<p\/><\/li>\n<li><a href=\"http:\/\/blog.retrosight.com\/SuccessFactorsForProgramManagersFromJoeBelfiore.aspx\">Charlie Owen &#8211; Success Factors for Program Managers from Joe Belfiore<\/a><br \/>      Maniacally focus on building a product your customers will love.<br \/>    (categories:  <a href=\"http:\/\/del.icio.us\/ajohnson1200\/software\">software<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/design\">design<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/microsoft\">microsoft<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/management\">management<\/a> <a href=\"http:\/\/del.icio.us\/ajohnson1200\/leadership\">leadership<\/a> )\n<p\/><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Fabulous Adventures In Coding : Future-Proofing A Design Quote: Premature generality is expensive. Designing code to be future-proof without a clear understanding of what the future holds often leads to excess generality; generality has very real costs, and they might be higher than the benefit accrued. (categories: software programming architecture change future-proofing ) Charlie Owen &hellip; <a href=\"https:\/\/cephas.net\/blog\/2009\/01\/29\/links-1-28-2009\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Links: 1-28-2009<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/1150"}],"collection":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/comments?post=1150"}],"version-history":[{"count":0,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/posts\/1150\/revisions"}],"wp:attachment":[{"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/media?parent=1150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/categories?post=1150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cephas.net\/blog\/wp-json\/wp\/v2\/tags?post=1150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}