Image
EAN-139780312626686   EAN-13 barcode 9780312626686
Product NameNickel And Dimed: On (Not) Getting By In America
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:0.9 inches / Length:8.2 inches / Weight:0.55 pounds / Width:5.4 inches
Amazon.comA Buy on Amazon ~ 0312626681
SKU9780312626686
Price New2.43 US Dollars    (curriencies)
Price Used1.06 US Dollars    (curriencies)
Width16.13 inches    (convert)
Height207.01 inches    (convert)
Length5.43 inches    (convert)
Weight8.8 ounces    (convert)
AuthorBarbara Ehrenreich
Page Count256
BindingPaperback
Published08/02/2011
FeaturesBest
Long DescriptionOur sharpest and most original social critic goes "undercover" as an unskilled worker to reveal the dark side of American prosperity. Millions of Americans work full time, year round, for poverty-level wages. In 1998, Barbara Ehrenreich decided to join them. She was inspired in part by the rhetoric surrounding welfare reform, which promised that a job -- any job -- can be the ticket to a better life. But how does anyone survive, let alone prosper, on $6 an hour? To find out, Ehrenreich left her home, took the cheapest lodgings she could find, and accepted whatever jobs she was offered. Moving from Florida to Maine to Minnesota, she worked as a waitress, a hotel maid, a cleaning woman, a nursing-home aide, and a Wal-Mart sales clerk. She lived in trailer parks and crumbling residential motels. Very quickly, she discovered that no job is truly "unskilled," that even the lowliest occupations require exhausting mental and muscular effort. She also learned that one job is not enough; you need at least two if you int to live indoors. Nickel and Dimed reveals low-rent America in all its tenacity, anxiety, and surprising generosity -- a land of Big Boxes, fast food, and a thousand desperate stratagems for survival. Read it for the smoldering clarity of Ehrenreich's perspective and for a rare view of how "prosperity" looks from the bottom. You will never see anything -- from a motel bathroom to a restaurant meal -- in quite the same way again.
Similar Items9780070282155: American Government (Schaums' Humanities Social Science)
9780070279476: Introduction To American Government (Mcgraw-Hill College Review Books Series)
9780060974992: Savage Inequalities: Children In America's Schools
9780060973339: Fear Of Falling: The Inner Life Of The Middle Class
9780060928285: America's Dream
9780060192686: Happy Hours: Alcohol In A Woman's Life
9780023956225: Work Motivation In Organizational Behavior
9780023890185: American Government (Schaums' Humanities Social Science)
9780006510130: The Other Side Of The River: A Story Of Two Towns, A Death, And America's Dilemma
9780006280033: Dead Man Walking: The Eyewitness Account Of The Death Penalty That Sparked A National Debate
View 59 more similar items
Created01-12-2013 1:23:51am
Modified04-30-2020 6:12:44pm
MD53582e3463f8c08cf0fa79bb194749def
SHA256a9726cb353486ca2da3a1f68749db55187f353870d762d197a1b1269dc9c9b7b
Search Googleby EAN or by Title
Query Time0.0180740

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share