I tend to agree with you. When I write scripts, I target sh, not bash. If it doesn't fit in sh, then I look at a dedicated scripting language (perl/ruby/python) that will almost certainly be a better fit.
This makes a lot of sense, and meshes with my own experience. I've created a lot of programs that collect data using Python/Ruby/similar and then use R for the analysis.
While using two languages is an overhead, it feels like it plays to the strengths of both sides.
Congrats to the Zite team. You made one of my favorite apps, and whether you continue development at CNN or move on to other ventures, I wish you the best and look forward to seeing what you do next.
Zite is one of the most used apps on my iPad, and has been for ages. I would've happily given you a few dollars for it, but I guess this worked out well for everyone.
If you're on FreeBSD you can use dummynet to simulate packet delay and loss.
It's quite handy. My partner has slow, unreliable, high-latency Internet in his house and there are an entire class of performance problems that are extremely obvious when I work from his place that are barely measurable when I work from a 100mb line that's only a few milliseconds away from a major datacenter.
You know nothing about the people you judged except that they threw a coffee into a virtual 'give a coffee / take a coffee' tray. And from that, you've extrapolated that they care more about art than world hunger.
Being a fast-follower is often an excellent strategy.
I've long thought that somebody will make a fortune by setting up a company that clones successful America-centric startups into Europe, Asia and/or Brazil; using a fast-follower strategy to test core ideas, but then implementing them in untapped markets.
I don't agree that ACSOI makes sense. Marketing isn't just the initial customer acquisition cost. It's also a substantial expense that keeps existing customers active, engaged and profitable. If it was just about customer acquisition then we'd never see an ad for Tylonel, Coke or Budweiser.
Fortunately Groupon is issuing a new S-1 tomorrow, so it's likely that those who are looking for more information will get it.
It'd be trivial to sort the calls by listening to a few seconds of each to identify potential high value phone numbers (banks, florists, catalogue ordering lines, etc), then listen to every call to the high-value numbers.
The only blessing in this story is that the miscreants made their damage so plainly obvious that the problems were identified quite quickly.
If they'd been a bit more subtle and a little patient, they could've engaged in massive identity theft and financial fraud without ever making it clear that AirBNB was the attack vector.
I'd argue that the existing system does just that.
The big boys have portfolios of patents that they fling at each other until some sort of cross-licensing deal is reached, whilst smaller players just have to cross their fingers and hope that nobody decides to tax them too extravagantly.
I omit the possibility of creating non-infringing products simply because it's virtually impossible to bring any meaningful product to market without infringing on somebody's overly broad patent.
For any project, you're always balancing quality, schedule, budget, scope and risk to try to get the best business outcome. Because of this, I don't believe in any of the hard and fast rules about the "right" way to code. It's far too situational.
That said, you make an excellent point about the importance of project prioritization. A management team who is good at identifying high ROI projects will stomp all over one who sprays pointless change requests at their dev team.
I'd argue that USAA is already trouncing BankSimple.
USAA competes with the same sort of value proposition (convenient banking with great service, but without a B&M presence), and is a fortune 500 company with millions of happy customers.
It's hard to find discussion about retail banks on the Internet without finding satisfied USAA customers telling their stories.
Some people might also be concerned that the note about sending emails wasn't added to the post until after there was mass outrage at the lack of notification. Makes it feel very inauthentic, as though they were really hoping they'd be able to sweep it under the rug.
I think term limits are probably ineffective, if only because so many staff stick around even as the names on the offices change, and they hold so much of the power.
Can you provide me with one or two examples that are 50x slower on pg than my? We're a postgres-heavy shop, and would be interested in finding solutions to any such problems that you can identify.
I routinely work with vendors who make non-contractual promises, where the only recourse is damage to their reputation and the probable loss of me as a client if they break them.
Not everything needs to be a contract or a lawsuit. Sometimes it's fine to take a man at his word, and then simply tell him to walk away if his word is no good.