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
One of the biggest challenges of large software projects is designing for change. Supporting fast-evolving new use cases. Being able to sustainably expand the project over long periods of time. This is why simplicity, modularity, and disentanglement are of the utmost importance.
There are definitely principles -- at least strategies -- that can help you design for change. But every project is unique, existing in its own context. There is no exact formula.
Are edge use cases important? Like I get wrapped up in them sometimes, and I'm just wondering if I'm wasting too much time with them.
"Simple things should be simple, complex things should be possible". Make sure there is a path forward for niche use cases, even if it requires more effort on the part of the user. But do not compromise the usability of simple cases for the sake of supporting niche ones.
Finally someone gets it. Tell that to the folks IIBA and PMI.
So true. Modularity allows SW to be readable, testable and debuggable as well.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
