I find coding disturbingly addictive. My brain starts racing — solving one problem presents another, onward and onward, to the expense of other work that needs to get done. It makes one feel clever, and feeling clever feels good.
Show this thread
Today's case in point: Leaflet's Circle object looks great, but near the poles the fact that it is not a true "Great Circle" algorithm becomes *very* evident. The solution? Write a new class that implements a "true" GC algorithm using Leaflet polygons. Not too difficult...
-
-
But then I think: these don't look quite as good as those crisp Leaflet circles. It'd be a shame to swap in something technically better but aesthetically ugly. Is there a way around it? My brain shouts: I BET THERE IS LET'S SOLVE IT WOULDN'T THAT BE CLEVER
Show this thread -
So now I have a class that uses a clean circle at most latitudes, but seamlessly switches to a more accurate (though also more ugly) version near the poles. (This is now live in NUKEMAP if you want to experiment.) Good fun, great rush. BUT... I've just lost an hour of other work.
Show this thread -
"Why don't I have enough time to do everything I want/need to do?" I constantly ask myself. "BECAUSE YOU'RE ADDICTED TO INTERESTING IDEAS AND SAY YES TO TOO MANY OF THEM," my brain shouts back to me, cruel as it ever is, but accurate. "ALSO YOU TEACH TOO MUCH," it adds.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.