Cognitive Load Handbook Discussion

[zakirullin]

Hi there!

The handbook was already discussed in several places:
It's Not That Complicated - Runtime Rundown Podcast
/r/golang (Highlight: DDD)
/r/programming (Highlight: HTTP Statuses & Featureful Languages)
issues (Highlight: Onion Architecture)

Contributions made by the community: #12 (credits to @erni27)

[MichaelBreeden]

Nice article...
And all us old timers are thinking "that's what I thought all along, luckily I kept doing it because it worked".
The claim that a class method should only be a few lines of code just doesn't make sense in the real world. It should be whatever length it takes to do the job. Never jump half way across a chasm because you like making small leaps. That is especially true for maintaining and debugging.
... I could go on. DevOps... Really, a developer is supposed to keep track of all that and be able to instantly switch between numerous roles that used to belong to a number of people? No cognition problem involved there! Better still, add cloud technology and security requirements. It will make the job more interesting and fulfilling.

[zakirullin]

@MichaelBreeden Thanks for your warm feedback!

The claim that a class method should only be a few lines of code just doesn't make sense in the real world. It should be whatever length it takes to do the job.

Exactly! There are so many rules and architectures that we've been blindly following just for the sake of it.

Whereas in reality the answer to the question of whether or not to apply an approach is: "It depends".