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
There are arguments to be made for both dynamic and static languages being good for moving quickly or accommodating change, often in the context of a startup. And it's true for both, except that a static language only lets you move quickly between correct programs.
That's not to completely dismiss dynamic languages. A program which isn't correct can still have merit and can provide useful feedback to guide the programmer, even when broken in part. Static languages trade that early feedback for the confidence that their programs are correct.
The curate's program. "Dear me, I'm afraid your program's not correct!" "Oh, yes, my Lord, really – er – some parts of it are very correct."pic.twitter.com/HW8xyjH89a
Note dynamic typing doesn't mean that the program isn't correct. Often programs are correct, even if the correctness cannot be demonstrated. Of course, as programs evolve, dev's intuition about correctness goes away. Only works as long as you can keep it "in your head".
For establishing correctness, automated tests work too — which is what dynamic typing proponents often talk about — except it's not the same thing (exists vs forall).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
