{"id":10871,"date":"2017-11-28T15:59:17","date_gmt":"2017-11-28T23:59:17","guid":{"rendered":"https:\/\/www.seedcode.com\/?p=10871"},"modified":"2017-11-28T15:59:17","modified_gmt":"2017-11-28T23:59:17","slug":"works-documenting-decisions","status":"publish","type":"post","link":"https:\/\/seedcode.com\/works-documenting-decisions\/","title":{"rendered":"What Works &#8211; Documenting Your Decisions"},"content":{"rendered":"<p>As we prepare to bring some new developers\u00a0on board, it\u2019s worth taking a look at a few of the things we do that make us successful. Sometimes we internalize these things and, not having had to explain them to anyone for a while, they kind of dissolve into habit. Or dissolve into habits we don\u2019t think we need to practice anymore. Documenting our coding decisions is one of the reasons we can support so many customers with such a small team. It&#8217;s easy to overlook, but it works.<\/p>\n<p><em>This is the second post in a series that formed the basis of my 2017 DevCon session on Increasing Code Quality While Staying Lean. Check out the first post for an <a href=\"\/what-works-video\/\" target=\"_blank\" rel=\"noopener noreferrer\">introduction to the series<\/a>. We&#8217;re looking at techniques that have made a big impact at SeedCode and we hope you&#8217;re inspired to incorporate some of these into your work.<\/em><\/p>\n<h2>Documenting Decisions &#8211; We&#8217;re Coding for Our Future Selves<\/h2>\n<p><a href=\"https:\/\/en.wikipedia.org\/wiki\/Total_Recall_(1990_film)\" target=\"_blank\" rel=\"noopener noreferrer\"><img fetchpriority=\"high\" decoding=\"async\" class=\"alignright wp-image-11090\" src=\"https:\/\/www.seedcode.com\/wp-content\/uploads\/2017\/11\/Arnold-300x271.jpg\" alt=\"\" width=\"260\" height=\"235\" srcset=\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Arnold-300x271.jpg 300w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Arnold.jpg 600w\" sizes=\"(max-width: 260px) 100vw, 260px\" \/><\/a><\/p>\n<p>We\u2019re coding for our future selves\u2014both in our products and in custom work. We end up coming back to our own code months later and sometimes it\u2019s as opaque to us as if we\u2019d never written it.<\/p>\n<p>So when we make decisions, we want to document them so that our future selves (or our teammates) can more quickly pick up the thread when they return to our work.<\/p>\n<p>This means you can restart projects more quickly, which in turn increases the delivery velocity: especially the velocity of delivering\u00a0change requests and bug fixes.<\/p>\n<p>[bctt tweet=&#8221;One definition of fragility: the original developer is the only one who can help this customer.&#8221; username=&#8221;seedcode&#8221;]<\/p>\n<p>Here&#8217;s what we do:<\/p>\n<ul>\n<li>When we comment out or change code in a script or in a calculation, we include a note in the comment about why we did it.<\/li>\n<\/ul>\n<ul>\n<li>If work is related to a <a href=\"https:\/\/manuscript.com\" target=\"_blank\" rel=\"noopener noreferrer\">Manuscript<\/a>\u00a0case, we include the case number in the comments: it\u2019s amazing to be looking at an If() statement you don\u2019t think should be there and see this telling you <em>exactly<\/em> why it\u2019s there\u2026 \u201cIf filter is not empty and field DOES NOT match this source: Case\u00a030325\u201d. Now you can go read that case and see the real-world situation that required the If() statement.<\/li>\n<\/ul>\n<p><!--more--><\/p>\n<ul>\n<li>When we\u2019re building a new feature and we decide between competing alternatives we write about that in the case or in the product docs. (For an example, see \u201cWhy Make This a Switch?\u201d toward the bottom of the article\u00a0<a href=\"http:\/\/www.seedcode.com\/pmwiki\/index.php?n=DayBackForFileMaker.PerformScriptOnServer\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>).<\/li>\n<\/ul>\n<ul>\n<li>Sometimes we start docs for features that haven\u2019t shipped yet so we have a place to record the details of implementation as we\u2019re creating them. It\u2019s much easier to jot down these details as we\u2019re building than to try and reconstruct them later.<\/li>\n<\/ul>\n<ul>\n<li>In FileMaker, any script that\u2019s changed gets the Manuscript\u00a0case number related to that change added to the header comments in the script. For products, we also include the build number we&#8217;re working on. This means that if we want to see all the scripts changed in a particular build, we can just use <a href=\"http:\/\/www.dracoventions.com\/products\/2empowerFM\/family\/developer.php\" target=\"_blank\" rel=\"noopener noreferrer\">The Tool<\/a> to search for the build number across all our scripts. (We used the FBz prefix when Manuscript was called &#8220;FogBugz&#8221;.)<\/li>\n<\/ul>\n<p style=\"text-align: center;\"><a href=\"\/wp-content\/uploads\/2017\/11\/scriptlg-2.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"aligncenter wp-image-10916 size-full\" src=\"https:\/\/www.seedcode.com\/wp-content\/uploads\/2017\/11\/scriptsm-2.png\" alt=\"\" width=\"1100\" height=\"654\" srcset=\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/scriptsm-2.png 1100w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/scriptsm-2-300x178.png 300w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/scriptsm-2-1024x609.png 1024w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/scriptsm-2-768x457.png 768w\" sizes=\"(max-width: 1100px) 100vw, 1100px\" \/><\/a><\/p>\n<ul>\n<li>And all commits to our repo (we use <a href=\"https:\/\/www.fogcreek.com\/kiln\/on-demand-infrastructure\" target=\"_blank\" rel=\"noopener noreferrer\">Kiln<\/a> and GitHub) should include the case numbers related to that work. When we do that, our commits flow back into Manuscript, linking the commit to the customer. When we&#8217;re reading back through cases and wondering if we really solved \/ shipped this, the case numbers help\u00a0us know for certain if and when we shipped a fix\/feature.<\/li>\n<\/ul>\n<p style=\"text-align: center;\"><a href=\"\/wp-content\/uploads\/2017\/11\/caseslg-2.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"aligncenter wp-image-10914\" src=\"https:\/\/www.seedcode.com\/wp-content\/uploads\/2017\/11\/casessm-2-973x1024.jpg\" alt=\"\" width=\"800\" height=\"842\" srcset=\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/casessm-2-973x1024.jpg 973w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/casessm-2-285x300.jpg 285w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/casessm-2-768x808.jpg 768w, https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/casessm-2.jpg 1100w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/a><\/p>\n<h2>Recent Ideas<\/h2>\n<p>[bctt tweet=&#8221;We write code once, but we support it forever.&#8221; username=&#8221;seedcode&#8221;]<\/p>\n<p>Well, sometimes we write it more than once \ud83d\ude09<\/p>\n<p>But\u00a0all of these strategies\u00a0are about creating a <strong>path<\/strong> from the customer\u2019s cases (or feature specs) to the code that addresses them\u2014a path that our future selves can follow. Creating a path means <strong>making links<\/strong> between things, not just comments. So paste in URLs and case numbers along with your comments.<\/p>\n<p>Having a path reduces restart time and increases role portability. Meaning your organization (not just your code) is less fragile: less susceptible to schedule changes, minor emergencies, or one of your developers just having a low energy day.<\/p>\n<div class=\"grammarly-disable-indicator\"><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n<div class=\"grammarly-disable-indicator\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>As we prepare to bring some new developers\u00a0on board, it\u2019s worth taking a look at a few of the things we do that make us successful. Sometimes we internalize these things and, not having had to explain them to anyone for a while, they kind of dissolve into habit. Or dissolve into habits we don\u2019t think we need to practice anymore. Documenting our coding decisions is one of the reasons we can support so many customers with such a small team. It&#8217;s easy to overlook, but it works. This is the second post in a series that formed the basis of my 2017 DevCon session on Increasing Code Quality While Staying Lean. Check out the first post for an introduction to the series. We&#8217;re looking at techniques that have made a big impact at SeedCode and we hope you&#8217;re inspired to incorporate some of these into your work. Documenting Decisions &#8211; We&#8217;re Coding for Our Future Selves We\u2019re coding for our future selves\u2014both in our products and in custom work. We end up coming back to our own code months later and sometimes it\u2019s as opaque to us as if we\u2019d never written it. So when we make decisions, we want to document them so that our future selves (or our teammates) can more quickly pick up the thread when they return to our work. This means you can restart projects more quickly, which in turn increases the delivery velocity: especially the velocity of delivering\u00a0change requests and bug fixes. [bctt tweet=&#8221;One definition of fragility: the original developer is the only one who can help this customer.&#8221; username=&#8221;seedcode&#8221;] Here&#8217;s what we do: When we comment out or change code in a script or in a calculation, we include a note in the comment about why we did it. If work is related to a Manuscript\u00a0case, we include the case number in the comments: it\u2019s amazing to be looking at an If() statement you don\u2019t think should be there and see this telling you exactly why it\u2019s there\u2026 \u201cIf filter is not empty and field DOES NOT match this source: Case\u00a030325\u201d. Now you can go read that case and see the real-world situation that required the If() statement.<\/p>\n","protected":false},"author":1,"featured_media":10873,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[34],"class_list":["post-10871","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-what-works"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>What Works - Documenting Your Decisions - SeedCode<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/seedcode.com\/works-documenting-decisions\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What Works - Documenting Your Decisions - SeedCode\" \/>\n<meta property=\"og:description\" content=\"As we prepare to bring some new developers\u00a0on board, it\u2019s worth taking a look at a few of the things we do that make us successful. Sometimes we internalize these things and, not having had to explain them to anyone for a while, they kind of dissolve into habit. Or dissolve into habits we don\u2019t think we need to practice anymore. Documenting our coding decisions is one of the reasons we can support so many customers with such a small team. It&#8217;s easy to overlook, but it works. This is the second post in a series that formed the basis of my 2017 DevCon session on Increasing Code Quality While Staying Lean. Check out the first post for an introduction to the series. We&#8217;re looking at techniques that have made a big impact at SeedCode and we hope you&#8217;re inspired to incorporate some of these into your work. Documenting Decisions &#8211; We&#8217;re Coding for Our Future Selves We\u2019re coding for our future selves\u2014both in our products and in custom work. We end up coming back to our own code months later and sometimes it\u2019s as opaque to us as if we\u2019d never written it. So when we make decisions, we want to document them so that our future selves (or our teammates) can more quickly pick up the thread when they return to our work. This means you can restart projects more quickly, which in turn increases the delivery velocity: especially the velocity of delivering\u00a0change requests and bug fixes. [bctt tweet=&#8221;One definition of fragility: the original developer is the only one who can help this customer.&#8221; username=&#8221;seedcode&#8221;] Here&#8217;s what we do: When we comment out or change code in a script or in a calculation, we include a note in the comment about why we did it. If work is related to a Manuscript\u00a0case, we include the case number in the comments: it\u2019s amazing to be looking at an If() statement you don\u2019t think should be there and see this telling you exactly why it\u2019s there\u2026 \u201cIf filter is not empty and field DOES NOT match this source: Case\u00a030325\u201d. Now you can go read that case and see the real-world situation that required the If() statement.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/seedcode.com\/works-documenting-decisions\/\" \/>\n<meta property=\"og:site_name\" content=\"SeedCode\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/seedcoder\" \/>\n<meta property=\"article:published_time\" content=\"2017-11-28T23:59:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png\" \/>\n\t<meta property=\"og:image:width\" content=\"319\" \/>\n\t<meta property=\"og:image:height\" content=\"325\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"seedcode\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dayback\" \/>\n<meta name=\"twitter:site\" content=\"@dayback\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"seedcode\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/\"},\"author\":{\"name\":\"seedcode\",\"@id\":\"https:\/\/seedcode.com\/#\/schema\/person\/af42f3f8cbfc8652fb0ffbb3f46f260f\"},\"headline\":\"What Works &#8211; Documenting Your Decisions\",\"datePublished\":\"2017-11-28T23:59:17+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/\"},\"wordCount\":739,\"commentCount\":5,\"publisher\":{\"@id\":\"https:\/\/seedcode.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png\",\"keywords\":[\"What Works\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/seedcode.com\/works-documenting-decisions\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/\",\"url\":\"https:\/\/seedcode.com\/works-documenting-decisions\/\",\"name\":\"What Works - Documenting Your Decisions - SeedCode\",\"isPartOf\":{\"@id\":\"https:\/\/seedcode.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png\",\"datePublished\":\"2017-11-28T23:59:17+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/seedcode.com\/works-documenting-decisions\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage\",\"url\":\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png\",\"contentUrl\":\"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png\",\"width\":319,\"height\":325},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/seedcode.com\/works-documenting-decisions\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/seedcode.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What Works &#8211; Documenting Your Decisions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/seedcode.com\/#website\",\"url\":\"https:\/\/seedcode.com\/\",\"name\":\"SeedCode\",\"description\":\"Build the Software You&#039;ve Always Wanted\",\"publisher\":{\"@id\":\"https:\/\/seedcode.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/seedcode.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/seedcode.com\/#organization\",\"name\":\"SeedCode\",\"url\":\"https:\/\/seedcode.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/seedcode.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/seedcode.com\/wp-content\/uploads\/2022\/12\/SeedCodeLogo.png\",\"contentUrl\":\"https:\/\/seedcode.com\/wp-content\/uploads\/2022\/12\/SeedCodeLogo.png\",\"width\":595,\"height\":189,\"caption\":\"SeedCode\"},\"image\":{\"@id\":\"https:\/\/seedcode.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/seedcoder\",\"https:\/\/x.com\/dayback\",\"https:\/\/www.linkedin.com\/company\/seedcode\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/seedcode.com\/#\/schema\/person\/af42f3f8cbfc8652fb0ffbb3f46f260f\",\"name\":\"seedcode\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/seedcode.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f0c386c5b845ee7fe111b36b2d87e983811f1f549682de9597a934b9dfd45469?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f0c386c5b845ee7fe111b36b2d87e983811f1f549682de9597a934b9dfd45469?s=96&d=mm&r=g\",\"caption\":\"seedcode\"},\"sameAs\":[\"https:\/\/seedcode.com\"],\"url\":\"https:\/\/seedcode.com\/author\/seedcode\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What Works - Documenting Your Decisions - SeedCode","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/seedcode.com\/works-documenting-decisions\/","og_locale":"en_US","og_type":"article","og_title":"What Works - Documenting Your Decisions - SeedCode","og_description":"As we prepare to bring some new developers\u00a0on board, it\u2019s worth taking a look at a few of the things we do that make us successful. Sometimes we internalize these things and, not having had to explain them to anyone for a while, they kind of dissolve into habit. Or dissolve into habits we don\u2019t think we need to practice anymore. Documenting our coding decisions is one of the reasons we can support so many customers with such a small team. It&#8217;s easy to overlook, but it works. This is the second post in a series that formed the basis of my 2017 DevCon session on Increasing Code Quality While Staying Lean. Check out the first post for an introduction to the series. We&#8217;re looking at techniques that have made a big impact at SeedCode and we hope you&#8217;re inspired to incorporate some of these into your work. Documenting Decisions &#8211; We&#8217;re Coding for Our Future Selves We\u2019re coding for our future selves\u2014both in our products and in custom work. We end up coming back to our own code months later and sometimes it\u2019s as opaque to us as if we\u2019d never written it. So when we make decisions, we want to document them so that our future selves (or our teammates) can more quickly pick up the thread when they return to our work. This means you can restart projects more quickly, which in turn increases the delivery velocity: especially the velocity of delivering\u00a0change requests and bug fixes. [bctt tweet=&#8221;One definition of fragility: the original developer is the only one who can help this customer.&#8221; username=&#8221;seedcode&#8221;] Here&#8217;s what we do: When we comment out or change code in a script or in a calculation, we include a note in the comment about why we did it. If work is related to a Manuscript\u00a0case, we include the case number in the comments: it\u2019s amazing to be looking at an If() statement you don\u2019t think should be there and see this telling you exactly why it\u2019s there\u2026 \u201cIf filter is not empty and field DOES NOT match this source: Case\u00a030325\u201d. Now you can go read that case and see the real-world situation that required the If() statement.","og_url":"https:\/\/seedcode.com\/works-documenting-decisions\/","og_site_name":"SeedCode","article_publisher":"https:\/\/www.facebook.com\/seedcoder","article_published_time":"2017-11-28T23:59:17+00:00","og_image":[{"width":319,"height":325,"url":"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png","type":"image\/png"}],"author":"seedcode","twitter_card":"summary_large_image","twitter_creator":"@dayback","twitter_site":"@dayback","twitter_misc":{"Written by":"seedcode","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#article","isPartOf":{"@id":"https:\/\/seedcode.com\/works-documenting-decisions\/"},"author":{"name":"seedcode","@id":"https:\/\/seedcode.com\/#\/schema\/person\/af42f3f8cbfc8652fb0ffbb3f46f260f"},"headline":"What Works &#8211; Documenting Your Decisions","datePublished":"2017-11-28T23:59:17+00:00","mainEntityOfPage":{"@id":"https:\/\/seedcode.com\/works-documenting-decisions\/"},"wordCount":739,"commentCount":5,"publisher":{"@id":"https:\/\/seedcode.com\/#organization"},"image":{"@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage"},"thumbnailUrl":"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png","keywords":["What Works"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/seedcode.com\/works-documenting-decisions\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/seedcode.com\/works-documenting-decisions\/","url":"https:\/\/seedcode.com\/works-documenting-decisions\/","name":"What Works - Documenting Your Decisions - SeedCode","isPartOf":{"@id":"https:\/\/seedcode.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage"},"image":{"@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage"},"thumbnailUrl":"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png","datePublished":"2017-11-28T23:59:17+00:00","breadcrumb":{"@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/seedcode.com\/works-documenting-decisions\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#primaryimage","url":"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png","contentUrl":"https:\/\/seedcode.com\/wp-content\/uploads\/2017\/11\/Documenting.png","width":319,"height":325},{"@type":"BreadcrumbList","@id":"https:\/\/seedcode.com\/works-documenting-decisions\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/seedcode.com\/"},{"@type":"ListItem","position":2,"name":"What Works &#8211; Documenting Your Decisions"}]},{"@type":"WebSite","@id":"https:\/\/seedcode.com\/#website","url":"https:\/\/seedcode.com\/","name":"SeedCode","description":"Build the Software You&#039;ve Always Wanted","publisher":{"@id":"https:\/\/seedcode.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/seedcode.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/seedcode.com\/#organization","name":"SeedCode","url":"https:\/\/seedcode.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/seedcode.com\/#\/schema\/logo\/image\/","url":"https:\/\/seedcode.com\/wp-content\/uploads\/2022\/12\/SeedCodeLogo.png","contentUrl":"https:\/\/seedcode.com\/wp-content\/uploads\/2022\/12\/SeedCodeLogo.png","width":595,"height":189,"caption":"SeedCode"},"image":{"@id":"https:\/\/seedcode.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/seedcoder","https:\/\/x.com\/dayback","https:\/\/www.linkedin.com\/company\/seedcode\/"]},{"@type":"Person","@id":"https:\/\/seedcode.com\/#\/schema\/person\/af42f3f8cbfc8652fb0ffbb3f46f260f","name":"seedcode","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/seedcode.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/f0c386c5b845ee7fe111b36b2d87e983811f1f549682de9597a934b9dfd45469?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f0c386c5b845ee7fe111b36b2d87e983811f1f549682de9597a934b9dfd45469?s=96&d=mm&r=g","caption":"seedcode"},"sameAs":["https:\/\/seedcode.com"],"url":"https:\/\/seedcode.com\/author\/seedcode\/"}]}},"_links":{"self":[{"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/posts\/10871","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/comments?post=10871"}],"version-history":[{"count":0,"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/posts\/10871\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/media\/10873"}],"wp:attachment":[{"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/media?parent=10871"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/categories?post=10871"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/seedcode.com\/wp-json\/wp\/v2\/tags?post=10871"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}