Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Spending a lot of time in task overhead? Tasks are too small: try batching work together (which may take some re-organization). For this, many small loops is better than 1 loop that does many things (parallelizes better).
For "helper" functions, which in this context are functions that are not themselves a task, but called by tasks, you can still run into the danger of 1-line-per-function codebases. I'm generally not in that camp of "ideal function size" so not a problem here.
Here's the larger point, I think. Lots of things come down to preference in programming. It's nice to have a "preference" made clearer by something that the machine cares about. I wonder how many more "preferences" there are like this that we haven't found yet.
Moreover, "machine preference" will always win in the end. Machine preference is why DoD is in vogue right now. DoD works because it makes the computer faster and we've found a way to make it digestible to humans.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
