Often when writing or reviewing code, developers have a natural tendency to create an abstraction that avoids duplication upfront but evolves into a hairy situation as new use cases come. Kent C. Dodds in his recent talk at React Summit summarizes, demystifies, and visualizes this problem as well as a solution.
Are you the kind of programmer who prefers to never see the same code in two places, or do you make liberal use of copy/paste? Many developers swear by the Don’t Repeat Yourself (DRY) philosophy while others prefer to Write Everything Twice (WET). But which of these produces more maintainable codebases? I’ve seen both of these approaches lay waste to codebases and I have a new ideology I would like to propose to you: Avoid Hasty Abstractions (AHA). In this keynote, we’ll talk about abstraction and how you can improve a codebase by applying and creating abstractions more thoughtfully as well as how to get yourself out of a mess of over or under-abstraction.
Kent C. Dodd’s AHA Testing
AHA Testing 💡
The AHA Programming Principle stands for "Avoid Hasty Abstraction." I have specific feelings about how this applies to…
This blog post was referenced at the end of Kent’s talk shown above. As the name implies, it applied the same “Avoid Hasty Abstraction” principle to tests.
Building and Conveying Vision at Lead Dev Live
LeadDev hosts conferences designed with the needs and pain points of technical team leads in…