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
I mean when coding to avoid a problem you add a layer of indirection most of the time, but how you achieve the same without create a big mess of overhead?
Adding a layer of indirection is the problem. We need to stop teaching people that this is the right thing to do, or the default way of approaching a problem.
just out of curiosity why do you consider this addition of indirection a problem?
Because after you pile more than a couple layers on you have a huge tree of indirection, which isn't fun to climb.
It can be a lot easier to understand 1 function that is just a progression of (even complex) statements than trying to u derstand a function that calls into 3 different libraries and you have to either chase a bunch of source files, or resign yourselfto black box mentality.
It's not just about complexity of understanding either. I saw someone suggest this as a method of searching backwards through an array (in JavaScript): `arr.reverse().find(x => x === foo);` This is marginally "easier" to read than a reverse for loop. It is also 99% slower.
Yeah, I didn't want to get into perf things for fear of getting called a premature optimizer (I don't think I've ever optimized a function lol, I don't even really know how to profile). But just easiness is a huge benefit of straightforward code.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
