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
Concrete example from my own (painful) experience: if the architecture of your code forces every feature to touch thousands of lines of existing code, that problem won't be affected much no matter how you improve your tests, documentation... etc.
And it might be really difficult to fix an architectural problem incrementally. What should you do? I don't really know myself. Just try not to get into that situation in the first place!
The fixed time allotment does seem to preclude including large architectural changes in that time budget, but I think the idea still has merit: virtually every code base can benefit from small bundles of TLC time by people who know it well.
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.
