You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
To be fair, the point we're trying to demonstrate here is perfectly valid: as a piece of software ages, it becomes increasingly expensive to develop for. But these charts are just legendarypic.twitter.com/uQPGqIyDl9
It's so bizarre to chart the number of developers working on a piece of software over time and point to it as if it means anything. The recruitment pattern is baffling, what reason could there be for adding so many people for a single release?
If this is enterprise software, a more likely pattern would be the number of developers holding steady while development steadily gets harder. How would you even recruit and retain people if your codebase was that bad
Here's the payroll chart. But the most important chart is the missing one: revenue! None of the preceding charts are necessarily problematic if the product is making money. But this is entirely unacknowledged in the bookpic.twitter.com/XEOAVqHTMh
But also, a product that does very little needs very little code, but once you've written all your custom DSL or other code, new features start reusing things you have so less new lines needed. Also refactoring probably reduces lines of old code
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
