1,443 karma · joined March 23, 2009
[ my public key: https://keybase.io/kgrinberg; my proof: https://keybase.io/kgrinberg/sigs/WEI_d3HGjUIUBsOtsfBAyLlxPP2GxVWvgMAg5oxxwJE ]
That said - it's possible this has changed, but IIRC the Maps API terms specifically said you must use any results in conjunction with a map...
This was a while ago, so my memory may be failing me, but I'm fairly certain we had an alternate "recovery" address set up - just no one thought to send an invoice there, or call the phone number on file, or whatever... it was a "hey, you show no signs of having received the invoice, so we assume you're a PITA deadbeat and we're going to perma-delete the account for you!"
Moral of the story (from my perspective) - if a customer isn't responding to your invoice, it might just be that they don't have it... try to reach on them a side channel before cutting off service!
Bail is just insurance against the accused fleeing (which is why it's set to high for someone that wealthy - if it was a few million, he could afford to just give it up).
It does take some resources, so you typically don't see that sort of intelligent routing outside of the major cities (at least in the US), but the tech is definitely there (not that it couldn't be improved).
I'm not sure what the policy implication is - there's no easy rule here. But it's worthwhile to keep in mind that "information wants to be free, Yale can't decide how it's used" (an attitude that's a bit of a straw-man, but not too far from what some have argued here) ignores the reality that the next time the Yale faculty debate whether or not to collect and collate evaluations (or whether to have a numeric score component), they may well decide not to. (Which, of course, is a principle that applies to other cases of data collection - sometimes it's best not to collect it, just because you don't know how it'll be [mis-]used...)
So with that in mind, the implementation problems include:
1) There was very little notice given to the affected parties - the bill passed July 24, effective July 31. (This is somewhat unavoidable, since part of the stated purpose of the tax is to fund transportation projects in 2013 - so delaying its effects would be counterproductive to the underlying goal).
2) There's still quite a bit of ambiguity surrounding implementation, including - crucially - what's taxable and what isn't. MA DOR (the state's version of the IRS) has issued some FAQs [2] and clarifications - which, annoyance aside, have actually been helpful. However, they only begin to answer the very real questions that this presents for many businesses - but we're responsible for collecting the tax basically yesterday (first filing due September 20, to cover taxes starting August 1). I read today that DOR will issue additional clarification and guidance in October... which I can only assume will be retroactive. So we'll likely be forced to either charge some people an unnecessary tax, or take an unexpected 6% revenue cut, or possibly end up having to pay penalties. Merits of the tax aside, the uncertainty - inevitable with such a new rule! - is what's killer.
3) Broadly speaking, the distinction they're trying to draw in the law does seem a bit weird. As I understand it (and IANAL, but have talked to a few - all of whom are still trying to parse what this means), if I write a custom CMS "from scratch", that's still considered a tax-free service. If I train you on, say, Wordpress (or any open-source or commercial product, really), that's still tax-free as well. If, however, I build a plugin to integrate Wordpress with your in-house SSO system - that's taxable. A custom theme? Probably.
Where do frameworks fit in? (Say, if I write you a shiny, custom CMS in Django). I don't know. There's a specific clarification issued by DOR that operating systems are exempt - or rather, to quote directly: "Custom application software (including custom software that incorporates such proprietary code) that is designed to run on a prewritten operating system is treated as custom software and not as a modification of the prewritten operating system software."
There are some interesting caveats being carved out - for example: "Suppose a computer system is designed but not actually built, so software is never actually integrated with hardware. Are the services still subject to sales tax? No."
Again, while on the whole I'd of course prefer that this tax go away entirely, at the end of the day it's no more or less rational than the taxation (or non-taxation) of many other goods and services. The critical problem here is the implementation, which introduces a whole lot of uncertainty and risk into a business that, until a few days ago, has never had to deal with this sort of thing.
[1] http://www.mass.gov/dor/businesses/help-and-resources/legal-...
[2] http://www.mass.gov/dor/docs/dor/law-changes/faqss-computer-...
I guess we will (might?) find out soon enough.
One of the virtues of having an on-site yoga studio has to be that you can take a break during the workday... but if there's a reasonable expectation of being reachable, asking everyone to leave work at the door 100% isn't totally realistic (and might mean that some people can't participate).
So while the normal rules of courtesy still apply, and the person receiving the call should probably step out if the call looks like it's going to drag on, the setting does matter.
I can't fairly condense the salient points, so I'll just encourage you to watch the video - it's long, but well worth it. I can honestly say it changed how I evaluate these sorts of situations (aside from being a very fine round of debate, but that's more of an acquired taste).
(Just to be clear: I was not one of the debaters, just happened to be lucky enough to be in the audience).
That gives you a more atomic process and several points to back out gracefully if something goes wrong, without having to worry about *.pyc files or any similar cruft.
BUT - to your average BigCo (which, at least judging from the Customers page, is the target market), a few $k/month is a rounding error in the coffee budget - particularly when compared with the labor costs for a "webmaster" whose job often consists of 20% content production and 80% helping the Marketing department use Wordpress.
Problem 1: the actual upload(s) of the XAP to App Hub just failed sporadically - we got an opaque error code which, when we looked it up, translated to essentially "either there's a problem with your language settings... or there was a random network error." Eventually it just worked, with no rhyme or reason - one out of every few times, it would get through.
Problem 2: the first time we were able to complete the submission, the app was rejected because we had marked it for worldwide distribution. Turns out the [free] app was barred from three countries (China and I forget the other two) because it had a few "inappropriate" images (of museum exhibits). OK, fine, some countries are censorship-happy - not MS' fault. So what does MS do? Reject the app wholesale (rather than just in the problematic countries). We resubmit (going through all the difficulties of #1 above), exclude the problematic countries from the "where do you want your app available" checkboxes... and wait as it goes through the full 5-business-day approval cycle.
Problem 3: OK, the app is certified and made it into the store! Woot! But wait - it has a pretty serious bug - can't play any audio! (It's a museum tour, so that's rather unfortunate!) The bug didn't exist in the version we tested (in the emulator and two real devices), and after several days of back-and-forth with MS, they acknowledged it was a bug in the "XAP ingestion" process (what App Hub does to your XAP once it's submitted). They suggested a workaround, which we implemented right away (it was trivial, albeit not-really-obvious). At that point - this is after talking to several-layers-up support engineers - we asked that they push our update to the store ASAP (given that it was their bug we were working around). The best they could do is "expedite" the certification/approval process, which still took 3 or 4 business days - which doesn't sound like a lot, but is pretty absurd given that the update fixed a showstopping bug which was the result of MS's own submission process.
All in all, it took several weeks from completion to actually appearing in the store - which is better than the App Store at its worst, but not exactly awesome... and, FWIW, we only started getting real answers after several layers of escalation (which I suppose isn't terribly unusual, but again, not really confidence-inspiring).
What I found particularly absurd is that while there were some technical issues with the platform, they were pretty minor in the grand scheme of things - bugginess-wise, nothing worse than what you encounter on Android... but the App Marketplace submission and approval process was an unmitigated disaster, and is of course the thing that you have the least control of.
I suspect most people (that is, developers who use the framework but don't necessarily contribute to it) probably couldn't tell that a BDFL has basically been MIA - it doesn't feel like development's stopped altogether (although again, yes, it can obviously be sped up, everyone's got their own pet features, etc.)