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's no such thing as explicitness or implicitness in software. There's a large number of decisions the software must make, and as the end user, you can only specify a tiny number of them. Good software surfaces the decisions you care about and takes care of the rest.
99% of decisions always have to stay hidden. Unless you're the one writing the software, implicitness is just the default, universal state of software tools. What matters is *which* bits are being surfaced at the tip of the iceberg. And that's an API design question.
So don't tell me, "this is implicit / this is magic." Tell me, "I care about configuring X." And do realize that software tools can be used by a variety of people, who don't all care about the same things.
This is true in organizations as well. Good employees make many decisions themselves and only bubble up a few important ones to managers.
Indeed, no one wants a program with a hundred features that make it confusing to use and unfriendly to the user, there are a lot of decisions that go into programming, but the whole time you question them with "will this benefit the user?" and "does this fit the brief?"
while I get the drift and mostly agree, I do think that the semantics of the hidden assumptions/decisions need to be clear to the user to avoid an unexpected outcome
Note: there are implicits in Scala, literally IMHO, they are good; they allow focusing the attention on what matters Note: analogously, too much documentation is a disservice: makes finding the relevant part harder. Laconism is underestimatedhttps://twitter.com/trylks/status/1263989420035903489 …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
