downshift - μ/acc pfp
downshift - μ/acc
@downshift.eth
AMA
16 replies
2 recasts
16 reactions

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
Strongest programming opinion of yours
2 replies
0 recast
2 reactions

downshift - μ/acc pfp
downshift - μ/acc
@downshift.eth
“DRY” (don’t repeat yourself) is way over-prescribed it is better to repeat boilerplate code than abstract it UNLESS the boilerplate frequently causes bugs…. then, abstract (h/t @subtlegradient)
2 replies
0 recast
6 reactions

TOM pfp
TOM
@subtlegradient
“Separation of concerns” is bad and wrong. Better: “avoid unintended coupling” Often many separate concerns are highly coupled and we should expose that reality explicitly so that it’s easier to reason about
1 reply
0 recast
2 reactions