{"id":121,"date":"2010-06-18T22:57:46","date_gmt":"2010-06-19T03:57:46","guid":{"rendered":"http:\/\/www.jetpen.com\/blog\/?p=121"},"modified":"2023-06-26T10:29:56","modified_gmt":"2023-06-26T15:29:56","slug":"designs-are-useless","status":"publish","type":"post","link":"https:\/\/www.jetpen.com\/blog\/2010\/06\/18\/designs-are-useless\/","title":{"rendered":"designs are useless – like planning"},"content":{"rendered":"\n

“In preparing for battle I have always found that plans are useless, but planning is indispensable.” -Eisenhower (from Planning Extreme Programming<\/a>)<\/p>\n\n\n\n

I believe this is true, because “no plan survives contact with the enemy”<\/a>. In software, the enemy is in the form of dark spirits hidden within the code, both legacy and yet to be written. Because plans (the schedule of work to be done) are intimately tied to designs (models of the software), it must also be true that no design survives contact with the enemy. Any programmer who begins writing code based on a preconceived design will almost immediately feel the pain of opposing forces that beg to be resolved through refactoring; programmers who lack this emotional connection with their code are probably experiencing a failure of imagination (to improve the design).<\/p>\n\n\n\n

Therefore, I think we can return to the original quote and state its corollary: designs are useless, but designing is indispensable.<\/p>\n\n\n\n

All this is to say that for the above reasons, I think these ideas strongly support the notion that the process artifacts (e.g., Functional Solution Approach, Functional Design, Technical Design) are more or less useless, because as soon as they are written they are obsoleted by improvements that are discovered contemporaneously with each line of code written, but the act of producing them (the thought invested in designing) is indispensable to producing good software.<\/p>\n\n\n\n

This leads me to conclude that we should not fuss so much about the actual content of the artifacts, so long as they capture the essence to show a fruitful journey through designing—that problems have been thought through and decisions have been based on good reasoning. Worrying about the content being perfectly precise, comprehensive, and consistent ends up being a waste of effort, since the unrelenting act of designing will have already moved beyond the snapshot captured in the artifact.<\/p>\n\n\n\n

Coincidentally, this theme also aligns with the notion of a learning organization espoused by Lean<\/a>. The value of designing is the facilitation of learning.<\/p>\n","protected":false},"excerpt":{"rendered":"

Designing and planning go together. The process should not be about the artifacts. It is more about learning from the journey.<\/p>\n","protected":false},"author":1,"featured_media":2683,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[3],"tags":[15,12],"class_list":["post-121","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software","tag-architecture","tag-methodology"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t