Gattaca was very prescient and thought-provoking movie, one of my favorites. The story described a future where individuals are allowed or denied opportunity based on a genetic test at birth. I think the point was that technology cannot predict or limit the human heart.
That same idea applies here too. This article illustrates that there will be other, nuanced perils to bioinformatics besides rewarding genetic lottery winners and punishing losers. Genetic testing is a powerful tool that should be used wisely. Of course, it will be a bumpy road until society settles on what "wisely" means.
Well, Gattaca raises a bigger point that just "Should we discriminate based on DNA?" In Gattaca, people can choose to genetically enhance their offspring to attain certain qualities. The protagonist's parents chose to make him in a "natural" way and hence he was considered to be the less extreme version of Untermensch. The director chose to portray such policies / societal norms as morally wrong (primarily through an emotional appeal). But it doesn't touch upon the other side of this issue. How well did humanity perform after humans were artificially evolved into what by some could be considered a new species. Except a few discriminatory cases -- much less than say Women and other minorities experience at the moment -- Gattaca doesn't seem too horrible, with space ships and space colonization. The movie can be thought of as depicting a Neanderthal that happens to be stuck in a Homo Sapiens Sapiens dominated society, and after facing adversity -- eventually succeeds. I think the issue is larger than that. Perhaps it's trying to make us consider the possible collective benefits of Humankind as a whole if it were allowed to fast-track its natural evolutionary processes. After all, if all humans became "Homo Sapiens Sapiens Sapiens" wouldn't we be better off?
People are still forced to work under threat of starvation, upper class people still work in open plan offices, lower class people still handle dangerous chemicals.
Despite space ships the depicted civilization didn't improve a lot. (and that's just the work conditions - leisure time practically doesn't exist in the movie)
Building it with mil-spec parts can legitimately raise the cost. Generally, components have a higher failure rate early in their life, then that failure rate goes down, and eventually goes back up. Mil-spec components are the ones which survive the early failure rate curve, so you're paying for that component, plus the others which didn't survive, plus the initial wear-in process itself.
Now, the $1000 price point on this seems somewhat high, but is difficult to judge without more specific specs on what's in it.
I know that many fire departments and other first responders are very severely constrained by budgets. There's lots of interesting things out there, but they just don't have budget for gizmos which cost multiple tens of thousands of dollars. A $1000 price point seems much more feasible. Though if you throw this into a burning building, I wonder if it would survive to be used again.
Cameras are crazy cheap, less than a buck. Lenses may be expensive to design, but you might find something off the shelf to do what you need.
The expensive pieces probably go, in rough order: Case and mounting hardware, radio, reasonable quality sensors, embedded processor and support chips, power supply. Don't know where the cameras fit into that, since you want a bunch of them.
If you can't get a COGS under $200 you don't deserve to be in business.
I'd assume that these would end up being re-usable in many circumstances, though certainly not all.
It sounds like they still need to figure out the durability issue -- but at that point it could be re-usable in some cases I'd think (does seem like they'd figure out durability first though).
Generally it goes Consumer, Industrial, Automotive, Medical and then Military Grade when it comes to chips. Differences can include higher heat tolerances or additional fail safes, such as additional watch dog timers, etc.
You know that product {X} has arrived when it's assumed to be so mainstream that is's being used to describe functionality {Y} in sentences like "it's like {X} for {Y}".
Appreciate the feedback. No one likes blocking signups, myself included.
Trouble is, the app can't serve the user without having his or her email address on hand. I suppose I could rework the process so the user can give an email address after seeing how the interface works.
For those curious, the emails it sends are simple lists of links, sorted by keyword.
What you should do is ask them what they want to search for, then go and do the search and show the results. (It's OK if you show old results - not sure what your technical architecture is.)
Then invite them with: Have these results emailed to you every day, enter your email here:
Also, I tried to sign up using the login form - that's not cool. If there is no match put up a page say, no such account, would you like to create it?
I was looking at kinvey.com mentioned in the comment of the article while researching an alternative for Adobe Publish at work. Their 1-2-3 explanation on the home page is compelling, except for the 1 part. Yes, one should have the option of creating or extending a custom model, but why not have a library of pre-built solutions? "Here's our e-commerce starter kit, it's got a cart, products, customers, tax tables, and inventory management. Also we built an awesome back-end and some integrations with these payment processors." If you're building a BAAS, why not pick three or four common web-app types and make the models for them.