1,333 karma · joined March 21, 2008
Unfortunately, I’m going through a divorce right now so I can’t cancel that credit card. But, as soon as I’m free that’s on the top of my list of things to do to start living the rest of my life.
Sorry, but she’ll be suckered by another grifter selling another pipe dream next week.
Also, homelessness isn’t the problem we think it is. It’s millions of problems. Any solution will never help more than a subset of the homeless population. We need to iterate on small solutions to make progress.
Here's my fix: put the systems under the control of the Judicial branch. This way, Intelligence is not asking for permission, they are asking for access. The tech who does the search is going to answer to the branch of government that cares about the law rather than the branch of government that has the conflicts which create the rush to misuse the systems.
I guess my point is you don't get things like Mugshots.com because you run a fair and equitable justice system. You get Mugshots.com because some people want to get in on our prison system racket but they don't have enough money to bribe a politician.
action -> UI recognition of action -> display API response
For actions that succeed 99% of the time, I think the "UI recognition of action" can be the success state. For actions with higher failure rates, the "UI recognition" should be a spinner or something to show the user that work is being done.If you've got a project where it's not acceptable to show "success" -> "oops I mean failure", just go with the spinner all the time. But, it makes a huge difference if you respond to a click in < 100ms vs. > 100ms.