sherwin
The author raises the interesting point that if it's truly an exception, you're better off letting the system crash all together (especially in a webapp, where you're basically dropping a single request for a single user) -- and if it's an "expected exception", then you should be handling it directly.
I don't see how that reduces to "never use try/catch" though, since catching a specific exception (or types of exceptions) is a way of "handling it directly."
"How does it work?
We communicate with Snapchat's servers and pretend to be their mobile app. This gives us access to everything that you can do through the mobile app. For example, we can send messages, view (and save) messages, create new accounts..."
That's a detail that's not relevant at all to their "users" (the people sending in snapchats). It sounds like they're bragging about their circumvention of Snapchat's lack of an API.
I don't want to diminish the technical accomplishment here -- reverse an engineering an API and writing a Snapchat bot is impressive. But, as other posters have pointed out, they're likely violating the Snapchat terms and misleading their "users."
> Addressing this issue, Toni references the open spirit amongst coders working on open-source software. “There’s no reward system right now for open science. Scientists’ careers don’t benefit from it. But in software, everyone wants to see your GitHub account.”
This got me thinking. First, I think a large reason a lot of people (read: people in my bubble, mostly students / recent CS grads) use GitHub is precisely because of the prestige. I'd say the people who use GitHub without ever contributing to an open repo vastly outnumbers the people who do contribute. Instead, many people start using GitHub as a way to show-off their own projects -- the whole "GitHub as my resume" idea. But as more people do so, having a GitHub becomes a standard, and you get a positive feedback loop.
Second, how could we shift the status quo for science to associating prestige in an open system? I'm not familiar with the history of open source software, but I wonder if there are any parallels from how OSS grew that we could apply to science publishing.
Finally, there's a big systemic difference between doing collaborative science and writing open source software I can think of: the barrier to entry to software is much lower. A lot of hobbyist programmers contribute to open source projects (or at least have a GitHub account, which feeds more attention / prestige to the ecosystem), whereas it's pretty hard to contribute to science without both a graduate education and (in many fields) expensive equipment.
How to learn efficiently
In general I've been very pleased with voice search on Google Now -- just reading the blog post I wasn't too amazed by the examples they gave for iOS because it sounds identical to what Google Now provides. I assumed that Google would release these features for android before iOS, but am am surprised by the overwhelmingly positive comments others here have to say here. Can anyone do a comparison and shed some light?
I do have to say that Google Now is sometimes rather slow -- the voice recognition is very fast (type as you talk realtime) but web search can sometimes take 10+ seconds to load even when already connected to wifi. Other times, it just works.
Although I can see why having a prepackaged one-button solution would make sense, where Stripe takes care of the presentation / styling / inputs, so there actually is a change of context.
For the record, I use Stripe at my company, and I love it!
If you only need the second item in the range (the value), use the blank identifier, an underscore, to discard the first:
sum := 0 for _, value := range array { sum += value }
For me, there are many tasks that I know I enjoy, whose results I know I care about, yet, if left to my own devices, I don't go and do them because the activation energy is too high. I offer two examples: running (I always feel great afterward and I know it's good for me, yet it's a hassle to actually get out there and run) and working on side projects (I love learning and building, yet I don't do it as often because I get mentally blocked by how overhelming a project is before I begin).
Previously, I would make up excuses (I don't have enough time... too busy... much school work... overcommitted) and my personal projects languished as I got caught up in external commitments. The biggest tip in my productivity system is this: Every month/week/day, write down the one thing I most want to accomplish for that time period, that I would likely not accomplish otherwise. If I can accomplish that one thing, I can call that day/week/month a successful one. I track my progress and results as well.
With this one objective system, I found myself delegating time for these projects and implementing all sorts of hacks to reduce the energy barrier of starting these projects.
Another way to think of this is how you structure your priorities. Instead of saying 'I don't have time', try saying 'it's not a priority' [1]. This lets you tell exactly what you do care about, and frequently, that set of things you care about is still larger than the set of things you get done.
[1] http://online.wsj.com/article/SB1000142405297020335870457723...
Can anyone think of a way to get around this issue? Very cool idea by the way.
etc, and the entire construct can be assigned to a variable because it is an expression.
As an aside, ruby 1.9 also supports generic predicates for case statements through lambdas, which is very concise and powerful. Example: https://gist.github.com/838163, source: http://flazz.me/predicates-in-ruby-case-statements
Sexual harassment isn't a punchline
While this might not set a "high bar for the quality of information," the President's effort shows a level of commitment to both technological streamlining of government agencies and to transparency and is, at the very least, a step in the right direction.
However, I question who would get a Chromebox though, because the portability + battery life + instant on are no longer relevant in this case, and those were by far the biggest benefits for the Chromebook. For a little more (~400), you could get a very respectable machine running a more powerful OS.
Some general thoughts on my experiences with the Chromebook: As a general computing device, I thought it was more or less completely sufficient. I used it to take notes (google docs / evernote) in class and it was awesome for that (light and portable).
With more than 7-8 tabs, things can get slightly sluggish (read: not instantaneous). Running more than 15 or so and you start getting serious performance issues. This is less of a problem than I thought because it forces me to maintain focus (I regularly can have >100 tabs when using my desktop). Full screen 1080p video also was sluggish.
It has a shell, so you can SSH and code also.
Frequently less technical friends would ask "but ... it only runs chrome?" to which I respond "well what can you not do in chrome?" and they have a very hard time giving an example. With gmail / calendar / docs / evernote / your music web app service of choice / etc, almost everything can be done in the browser.
To be fair, I also use a powerful desktop for more intense tasks (photo editing, coding, and occasional gaming). I doubt I would use the chromebook/box as my primary computer.
Second, was anyone else slightly reminded of Steve Jobs in his earlier days? Maybe it's because I just read the Steve Jobs biography, but Chasen seems to demonstrate a lot of the same characteristics: desire for complete control over the product, strong vision, disregard for more practical matters (marketability, cost), belief that the product qualifies as art, and mild tendency to be reclusive, stubborn, or uncommunicative.
"I’ve narrowed it down, really boiled it down, to one core piece of advice. If I can only say one thing, and I don’t know you any better, it’s: don’t. Don’t do it. Seriously."
The key part here is "If I can only say one thing, and I don't know you any better" -- for MOST people, starting your own company is not a good idea! Especially if you'd be doing it for any of the misconceptions that Libin outlines.
However, it is odd that Libin chose such an approach given that he was speaking at a conference with a big emphasis on web start ups.
In fact I think it interferes with UX because it's harder to quickly read the list -- you need to wait for the animation before reading the text. The only exception to this is Skew (because the item text is always visible), but even that is harder to read than just a normal list without the animation.
Very impressive demonstration of CSS3, but just because you can doesn't mean you should.
which is almost certainly a broader algorithm that tries to semantically parse out factual information.
I wonder if this is intentional though; it seems very odd to depart from their traditional colors.