{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2025-02-26T01:23:16.076Z",
  "attributedTo":"https://gopinath.org/actors/rahul",
  "replies":"https://gopinath.org/objects/_mdHlpQl42c/replies",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://gopinath.org/actors/rahul/followers"],
  "content":"<p>Reading John Ousterhout's <a href=\"https://github.com/johnousterhout/aposd-vs-clean-code/blob/main/README.md\">conversation</a> with \"Uncle Bob\", regarding long methods, I do see value in shorter methods for a reason that does not seem to be mentioned here.  Given a long method, typical languages do not allow me to reason about what part of the method state (all variables that have been declared so far in that method) has an impact on a given section of the code. The larger the code section, the larger the cognitive burden. When I break up a large function into smaller functions even if those functions are not used elsewhere, I provide a contract that none of these variables that are not in the function have an impact on the function, and none of the variables that are declared within the function have an impact outside this function. This allows me to reduce my cognitive load.</p>",
  "mediaType":"text/html",
  "attachment":[],
  "type":"Note",
  "id":"https://gopinath.org/objects/_mdHlpQl42c"
}