I've been thinking a lot about domain-oriented OO vs pattern-oriented OO because domain-oriented OO is usually thought of as "unteachable," and that fact showcases the way developer education is broken.https://twitter.com/betsythemuffin/status/1006292902333607936 …
-
Show this thread
-
Domain-oriented OO is hard for current dev education paradigms for two reasons: 1. It is a subjective craft. Subjective crafts require art-school techniques, not "here's how pointers work." 2. It is not about building a static artifact. It is about building team understanding.
2 replies 2 retweets 43 likesShow this thread -
betsythemuffin Retweeted betsythemuffin
Most attempts to teach the “craft” of software have fallen flat because the “artisan” metaphor emphasizes individual work and a static end product. Software is a living system, created by teams collaborating with both themselves & past software versions.https://twitter.com/betsythemuffin/status/1006603473935306754?s=21 …
betsythemuffin added,
betsythemuffin @betsythemuffinIncidentally, I loathe the way that the self-congratulatory, individualistic wank of the "software craftsmanship" movement has poisoned the idea of "software-as-craft." Software is still a craft; it's just nothing like the craft Bob Martin thinks it is. https://twitter.com/betsythemuffin/status/1006598535314399235 …6 replies 12 retweets 58 likesShow this thread
Traditional craftmen used to work in master-apprentice relationships within artisan guilds emphasizing repeated practice in a tradition evolving across many lifetimes. Any equivalence of artisans with "individual work and a static end product" is bogus presentism at best.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!