I was shocked when I got to that part. Even aside from the specific jobs he mentioned, he seems to truly believe no one in the united states does physical labor that requires physical strength. Even being charitable one would have to at best assume he meant 'almost' no one which is still is profoundly disconnected from reality.
The experiment as a whole seems somewhat uninformed, there are many liquid diets intended for long term use which have been developed scientifically and the results of which have been studied for decades. I guess this is good for his own personal discovery, but I think his goal is also around making money... in which case if I were in the market for a liquid diet I would rather something that was designed by nutritionists, taken by thousands of patients,and scientifically reviewed... rather than a learn as you go tested on one individual
There are many people in the US for who "work" necessarily means physical work. From NPR (through the programs Planet Money and This American Life) on how so many Americans are on disability (http://apps.npr.org/unfit-for-work/):
Over and over again, I'd listen to someone's story of how back pain meant they could no longer work, or how a shoulder injury had put them out of a job. Then I would ask: What about a job where you don't have to lift things, or a job where you don't have to use your shoulder, or a job where you can sit down? They would look at me as if I were asking, "How come you didn't consider becoming an astronaut?"
Genuine question, is there a truly significant portion of American agriculture that is based on plowing by hand? I was under the impression that most food comes from commercial-level farms that use machinery to plow. My dad works on a pretty small farm, and they definitely don't do anything by hand at this point. I suppose that you could be referring to people who garden as a hobby, but I don't know if I'd count that.
Sugar beet field weeding used to be done by teams of migrant workers with handheld hoes. I think they've figured out how to not have the weeds in the first place with better pesticides. Most fruits and vegetables are picked by hand.
I guess I didn't realize this was about muscles. I was just replying to the guy asking if agriculture was done by hand. Maybe shouldn't follow threads via the /comments page. I end up not knowing what the context is.
Makes sense. I guess I just was imagining corn and grains, stuff that seems like it'd be easy to pick mechanically. Didn't really think about stuff like beets. Thanks for the answer though!
> Ideally you should create a great multipurpose validation library that does nothing but validation and then you create a second mini-library that encapsulates your validation library and connects it to jQuery and chainable.
Can you expand on this? I was hoping to implement a custom valildation library as I am also unhappy with $.validate(). Any links would be helpful, too.
First off, to do this right you should ideally be using a module system on your front end. Something like CommonJS, RequireJS or Almond.js are all acceptable choices.
Then for validation, you should create a validation with interfaces/apis similar to something like underscore.string.js. It should basically validate the content of form inputs, which will usually be strings and numbers. These functions should know absolutely nothing about the DOM or client-side javascript. They should only know about the data you are interested in.
Building your validation library like this means it can be used in at least three different ways:
(1) use like the library being discussed in this thread
(2) use at the model layer on the client-side with a framework like backbone.js or angular.js for examples
(3) use on the server side if you are using something like node.js that allows javascript execution.
Now once you have that general purpose data validation library, you can achieve use (1) by coupling it with a tiny adapter library via the module system of your choice. In this adapter library you require(your_validation_library) as a local var and then create a chainable jQuery interface that takes the `this` variable which is usually bound to the element currently being processed when creating a jquery plugin and pipes the val() of that element to the appropriate function in your validation library.
One way to do this is to have a one to one mapping between some DOM attribute value (like a classname or a custom data attribute like data-validation) and the functions in your validation library. With this approach, you get that attribute value from `this` and use a hashmap to determine what validation function (or functions if your hash map contsains arrays of function names as the value in the k-v pairs) is appropriate.
Wow. Talk about being disconnected from reality.