test code that has concrete business value
Abstractions that we'd rather replace shouldn't be a testing priority.
3 Matching Annotations
- Sep 2020
-
www.deconstructconf.com www.deconstructconf.com
-
-
the promise was that I would just be able to focus on this specific layer in my code and not actually care about all the layers. Is that really what happens? I'm sure most of you probably had this bug where you started one layer, oh, it goes here. And it's like, well, actually, no. You need to understand this layer and this other layer because the bug, it goes across all of those layers. And we have a very limited stack in our heads.
I create abstractions because I want the layers of my program to use simple concepts, in other words, concepts which hide lots of complexity. This is good when the code works as intended.
It may make tracing the execution of the program more difficult when something goes wrong.
-
abstraction creates accidental coupling
A and B use C. Now A and B are indirectly coupled to each other.
-