ericgoldberg

Interesting that communications lines are underneath water lines. The engineer in me wonders if that's a good idea, and also wonders if there's a good reason for it. Anyone have an idea?

Which theater? I'll start seeing films there :)

I don't think this problem is limited to just kids. This is something that annoys me about a lot of adults, lately. It often seems like conversations lately are devolving into people tweeting at each other in the physical world. Something I've noticed for the past several years, but seems to be gradually becoming a common way for people to communicate with each other "in the real world."

No, we do some client-side prefiltering to ignore non-products, and we also do some more extensive server-side filtering. We also allow you to cancel snap processing, as well as go into an "Ignore new snaps" mode via the settings in the app. Also, the upload only happens when the app is foregrounded, giving you further control.

We do our own searching and wrote our own crawlers. Does that answer your question?

Good question- with Safari, we use the visible domain to help score the confidence for mobile websites. For native apps, we don't have any such "easy" confidence boost. So we have to fingerprint the app based on different features present in the image that is captured.

The system is computer vision / machine learning based, so even on novel sites, it will get better over time with more usage and training. We've trained it up for a bunch of the most popular sites already though.

Does this make sense?

No, it detects the screenshots as you take them. (I helped build the app)

Nice, it's like Spy Party, but with an actual release. Nice job.

And a general lack of links throughout. Who doesn't hyperlink their table of contents? Or call a table of contents a glossary, for that matter...

Only after you find out they were getting filtered, usually because someone calls you to say "WhyTF aren't you responding to my emails?"

That's actually pretty cool. I hope the App Store allows animated gifs and/or videos soon. Some apps really look good when their Core Animation subtleties can shine through.

StumbleUpon has been doing this for a couple of year. I always liked the built-in pagination.

I think they buy a fair bit of their data from third party vendors, but I'm not positive. Still, aggregating and organizing all that information is impressive.

That's great and all, but a real screensaver provides a cheap way to lock a computer, and is functional and can be beautiful as well. This is beautiful, would love a screensaver of this to lock my computer when I step away from it.

This is amazing. I have 3 new SMS tones now. (See: http://www.microsoft.com/games/monster/downloads.htm )

It seems like this article is saying "H1B workers are not LITERALLY indentured servants, but here's a ton of reasons they are at a huge disadvantage." So basically the article is railing against the semantics of an exaggerated expression people use to highlight a problem everyone acknowledges exists.

Actually, a good code smell / architecture smell in a Rails app is if any given controller method is over 10-15 lines (And even that is on the large side IMHO). For example, I believe Code Climate specifically penalizes your score for long methods in controllers.

I write plenty of Rails apps that have thin controllers and fat models. Class methods / static methods on models can help encapsulate business logic in any language's MVC frameworks, as well as liberal use of the Tell Don't Ask pattern.

I think the font is decent, but I won't use it in its current iteration for the following reasons:

1. The lowercase 'm' is muddled and looks bad without anti-aliasing, downright horrible with anti-aliasing. 2. The lowercase 'k' is "too unique" and distracting (personal taste) 3. The lowercase 'e' is too squished and doesn't read well at small point sizes.

Overall, this font is not horrible. But with every "programmer-centric" new font that gets a bit of buzz, I always end up going back to non-anti-aliased Monaco within a day or two. It just seems like one of those perennial non-problems people keep having a go at.

It's telling that they don't know (or do know, but don't see the benefit in) RESTful interfaces. Which isn't a dead-end for the interview, it just leads to more questions to see what they understand about HTTP. I'm not expecting a particular answer, I'm using a question to understand where someone is at and then using the following discourse to understand how they arrived there.

Personally, I like using HTTP principles when interviewing web developer candidates. I'm not expecting people to know every detail of every RFC, or trivia type stuff in general. I more am interested in how much they know / can figure out about how HTTP-based communication works. I will ask stuff like "Explain how a redirect works, and how clients/browsers and servers interact with each other during a redirect." Also, REST is built on the concept of using HTTP verbs and resources properly, so it is nice to ask them to design a rough draft of an API to edit, add, delete, and list users via HTTP. Without asking them to do it RESTfully. It's telling if their first instinct is to have a "createUser" endpoint versus a POST to /users/

There are a few TED talks, including from the 2012 Life Hacks series, that partly address the issue of happiness.

For some reason, I can't see your username

I've tried alternative input devices, but never can get the hang of them. Too many years of traditional mousing, I guess.

For me, I use a free app called Time Out Free. It does scheduled micro-breaks of 15 seconds every 20 minutes. I just stand up or lean back, do neck and arm stretches, and get back to work in 15 sec.

There are a slew of other apps that do the same thing. This is just one I found a while ago and it's free.

Municipal bonds can be good. They have a historical track record of being pretty low-risk. Detroit being a glaring exception, however. If you want something more high-risk, high-potential upside, might not be for you. But if you want something with a greater return than a savings account, might be worth investigating.

nginx is a joy to configure and work with. I like the style of thinking of "OK, I'll run this on port 7001 and just use iptables to forward 80 -> 7001" Lets you run services as non-root, with the exception of the iptables one time setup.