altncatchfire
I've been playing through the archives, and they are challenging but fun. My criticism is that sometimes the answer is very ambiguous.
For instance, (spoilers ahead), in this case
> there[something golfers' apparently [scold, with "at"]]
I know the answer is "therefore". But the inner bracket could be shout/scream/yell.
It's quite frustrating when I get docked for this, hopefully the clues can be better constructed/beta tested in the future?
Thanks again for the fun game :)
Do you believe DDG will also eventually move to the subscription model for these features (unlimited aliases, reply to sender)?
The figure available was "billions". For ease of calculation, say it was 7b. That means if each developer pays $100 and total revenue was 7b, 1% of the world must be a developer. (1% of 7b * $100 = $7b)
Also, by your own figure, 20 million is already ~0.25% of the world population.
The value with IDEs is a smarter method for traversing code. It figures out exactly which function you mean, helping you get better context cues, auto-completion and traversals. This isn't particularly easy to emulate through simple command-line tools.
As for the language of the apology, you propose a very subjective reading of the text. "Taking up space" seems valid here as it concerns the man in the middle of this event. Instead of being "forbidden from dissent", it seems he already knew he was on the wrong side months ago and is simply attempting to focus the conversation towards more important things than himself.
import logging
got = "%d"
logging.warning(f"hi {got}")
logging.debug(f"hi {got}")
Output WARNING:root:hi %d
DEBUG:root:hi %d