Interesting post that conflates two separate issues: expressive flexible interfaces and code de-duplication. The bit about communication with team members is very important. More details
https://twitter.com/steipete/status/1216124320419926018 …
-
Prikaži ovu nit
-
The example replaces repetitive code with a neat (
literally) deduplicated abstraction. The problem with that is that it also tied down the interface to adhering to the chosen abstraction.1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit -
My proposed take is not to change the interface. Keep it as flexible as needed, that is few assumptions, to allow for easy specialization when necessary. Keep your code hackable to be agile
1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit -
Deduplication of the implemention makes sense though! It allows for better testing and reduces the chance of bugs
1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit -
Choose your interfaces wisely but decouple them from your implementations. This is a good pattern that gives you slack in both dimensions to tweak
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđaPrikaži ovu nit
A good blog post overall. Especially that it is important to communicate with team members before rewriting someone's code 
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.