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
Sometimes to make things work, I need to apply temporary hacks, like hardcoding a few values. I just decided that I'm going to put them all into a `Hacks` class, which I will demand as an implicit to any method which needs them. Now they're more visible and less forgettable.
I could have just made that object global, but making it an implicit forces every method which depends on a hack to pay a small cost in the form of a definition-site parameter: extra motivation to [re]implement hack-free solutions.
Great idea. Would it be worth splitting, in advance, into different categories e.g. mini hacks vs big hacks..? ;)
Hack prioritization can be a next step.
unsafe_ all the things
This reminded me of your `Internet` object for things that require internet connection. It's the same approach. 
Yes, I reminded myself of that just after I tweeted it!
Implicit to make it more visible
tbh I'd use an object anyway. Passing it implicitly requires infecting the entire call stack with it, and later you'll likely be removing all of that but only making actual changes at the use site (and probably a constructor param). YMMV
Yes, maybe. My intention was to document (with static code) which methods are relying on "hacks", directly or indirectly, but the cost of the "indirectly" ones may be too high.
Good idea. Like Unsafe in Java, Cats and Rust. And everyone will need it all the time...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
