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
What do you mean by "move quickly b/w correct programs"? I feel that's a good point, but I want to know more.
If you mean that you can refactor one program into another. Or that you can get back to a program, after you've forgotten what it is about. Yes, I agree 
I would say programs which don't crash. But no crashing and correctness are different things. You can have bulletproof program which works badly and has invalid logic implemented. Such program is not correct.
That's a good thing right? I mean, I'll rather put my focus on logic than possible runtime issues. More than willing to accept the compiler + strong type system help
https://www.haskellforall.com/2019/06/the-cap-theorem-for-software-engineering.html … Static languages value consistency over availability: can't run a program at all until it has compiled successfully.
Does Erlang have partition tolerance then?
I remember a chat with old colleagues about dynamic vs strong typing, we came to an interesting aspect that is related to the cognitive bias inherent to each developer. My self don't like to juggle too many balls at a time so I prefer static typing
I find way more easy to get familiar to a code base written in a static lang than a dynamic one. Even tho those tend to be more verbose, the logic gets better encoded in types, I feel like debugging when trying to understand dynamically typed programs
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
