We might be doing fine on average, despite it. Yet, there are seemingly links to autoimmune diseases and cancers, and still more research to do.

So maybe a good % of the population could be doing more fine without the micro plastics?

First off, I think the primary objective should be creating value for the company you work for. Bums in seats, lines of code written does not always produce value.

I think any position where you can automate away your daily tasks, and that's an expectation of the job, is great. There is no shortage of companies that maybe run on legacy software that requires a ton of effort to keep things running. You'd be surprised how often companies do things just because that's how they've always done it.

The other great option, which is what I did, is to become an important part of the team, and start negotiating for shorter work weeks.

I think you can find what you're looking for if you combine these strategies, and nobody would fault you on it.

Let's assume that we, like our employers, are rational economic actors seeking to maximize the returns we receive from our capital and labor. Then our primary objective in job with static hours and static compensation would be to expend the bare amount of effort needed to retain employment. Creating value for the company would be an auxiliary objective in support of retaining employment.

You and the OP seem to be basing your arguments off different assumptions.

Cool! If anyone likes these they should check out http://projecteuler.net/ as well.

UI looks inconsistent, but I see a lot there to be excited about. If they are taking cues from the phone OS, then that's a very good thing IMO. I've always felt that was one of the nicer mobile UI's.

I don't like this logo at all. It's too complicated and feels contrived.

The concept of just the shell was pretty cool, but the three colors doesn't add anything. I don't care what ideation process says, if it's not adding clarity or defining the brand then I'd say it's just complicating things.

That said, thanks for sharing.

I think the lighting is more impressive than the skin. Still, a cool tech demo!

> If HTML5 data-* attributes change during program execution, use jQuery's .attr() method to get the current values.

I'm not sure why anyone would want to use an attribute for storage, but this is good info. I for one love data-* attributes. It's better than the days of trying to pack info into the id or rel attributes.

Why not just add arbitrary attributes to HTML nodes (before the data- attributes were standardized)?

Is there some reason not to do that besides 'it would fail a validator test'?

The attributes you decide to use now may wind up in the HTML spec some day. If that were to happen, your site may break.

...I hear that a bit when this question comes up. Personally, I think the site would be due for an update by then anyway.

I just like how G+ helps me share internet jokes with my friends, and at the same time, still be within my anti-social comfort zone.

Your question tells me you have as good an understanding of the process as you need. Also, I think a good entrepreneur has a sense of what they can't do, ie. marketing, etc. That understanding comes with some failures as far as I can tell.