5,469 karma · joined January 9, 2009
However, after an internal review we realised that a lot of our UK properties have locations in Asia or the US... It turned out that typos in what3words often result in a valid location on the other side of the world. The most common mistakes we found were plural words instead of singular ones (e.g. "cats" not "cat") or the other way around.
Of course we could have improved the user interface or added some extra validations, but at this point we realised that what3words is more trouble than it's worth, and decided to migrate to storing lat/long directly. That allowed us to avoid a third-party dependency and simplify the code, since we had to cache lat/long anyway in order to plot properties on a map or calculate distances between them.
[1] https://en.wikipedia.org/wiki/Poland%E2%80%93United_States_r...
[1] https://gist.github.com/XVilka/8346728 [2] https://github.com/adambyrtek/dotfiles
In other words this was about the marginal costs of delivering content to additional viewers, not fixed production costs.
I used to preserve and organise all my digital life as well, but at some point I found it really liberating to just let things go. Storage might be cheap, but maintaining a comprehensive archive takes effort which could be better spent on future projects. In fact, I realised that treating historical data as ephemeral helps me achieve more and obsess less about perfection.
Of course this is just my personal opinion, different approaches work for different people.
This is definitely not true. Maybe you confused it with Isle of Man or Channel Islands, which are crown dependencies with certain autonomy, often accused to be British tax havens.
some | commands | grep ERROR
In fact I do this so often that I have it aliased to g: alias g=grep
Maybe I could achieve the same with ack/ag/ripgrep, but I somehow mentally associate these tools with searching over a filesystem.