nfw2

38 ms·

1. 571.▲
   by nfw2 6y ago

   Einstein himself would approve this philosophy. As he once said, "Everything should be made as simple as possible, but no simpler." Still, finding the simplest-possible solution to complex problems is often challenging in itself,
2. 572.▲
   by nfw2 6y ago

   When considering whether some abstraction is "right" or "wrong", another important thing to consider is how cleanly the abstraction fits into a mental model of how the program works. Good abstractions provide value outsi
3. 573.▲
   by nfw2 6y ago

   Yes, you should understand what a function does when you call it. Not everyone who looks at a codebase is modifying the codebase or adding new function calls. The person referencing the code may already be 1-level deep in parsing the impl
4. 574.▲
   by nfw2 6y ago

   1.) I think political and interpersonal issues can play a role here. People are often hesitant to suggest other people's code needs to be rewritten. This is especially true if an abstraction is heavily-used by the organization. If
5. 575.▲
   by nfw2 6y ago

   I agree that over-engineered helper function hell can be a real problem. I disagree strongly with strictly enforcing the 3x rule. The right abstraction can be helpful even if it is used only once. The right abstraction will communicate its
6. 576.▲
   by nfw2 6y ago

   https://www.youtube.com/watch?v=RZevgdbMIB0&feature=youtu.be... This is from Obama's town hall on June 3rd. The speaker is on the city council in Minneapolis, which seems to be leading the charge on this issue. *T