U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
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.
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 
Deduplication of the implemention makes sense though! It allows for better testing and reduces the chance of bugs 
Choose your interfaces wisely but decouple them from your implementations. This is a good pattern that gives you slack in both dimensions to tweak 
A good blog post overall. Especially that it is important to communicate with team members before rewriting someone's code 
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.
