Come the revolution, the WSJ will be first in line

-
This, and I swear this is true, is definitely not from The Onion.  Veronica Dagher writing in the WSJ (and with an accompanying oh-so-helpful video) explains how you can be broke on $400K/year.  In Chicago. (emphasis below is all mine)
They live comfortably, travel frequently and pay the mortgage on a home worth more than $1 million. They send their two teenagers to public school and put away about $12,000 a year for retirement and $10,000 for college tuition...
The couple's annual take-home income is $273,000 after setting aside money for retirement and college and after paying U.S. and Illinois income taxes...
They spend $87,000 a year on their mortgage, $24,000 on property taxes, $25,000 on home maintenance and $15,000 on utilities, cellphones and other household bills...Groceries for the family of four cost $575 a week, or $30,000 a year.
The family buys a new car every four years, which amounts to $15,000 a year on average, and spends $9,000 annually on car insurance. Their discretionary purchases also include $21,000 a year on dining out and other entertainment, $12,000 in membership dues at a local club, and $26,000 on two family trips and one weekend getaway for the parents.
Add in $10,000 for equipment, fees and other expenses related to sports their children play, $4,000 for gifts and holiday spending, and $5,000 for school fundraisers and other charitable giving.
Suddenly, the hypothetical couple is $10,000 in the hole every year.
Or, to put it differently, "Once we spend all our money, we have none remaining".
Which makes a tremendous amount of sense, because, clearly, saving $10K/year to break even by
  1. Spending only $11,000 a year on dining out is not an option
  2. Dropping the $12,000 membership at the local club is not an option
  3. Spending only $16,000 on vacations is not an option
  4. And god forbid, they move to a less expensive house!
Yeah, this stuff doesn't even need me to rant at it - it pretty much is an auto-troll.

/via WuMo

Comments

Post a Comment

Popular posts from this blog

Erlang, Binaries, and Garbage Collection (Sigh)

-
Image
The nice thing about garbage-collection is that it is makes memory management absolutely transparent to you Of course, the above is true right up to the point when it stops being transparent, at which point it does a phase change from nice to clusterf**k of biblical proportions .  There are entire posts, books, and suicide notes that have been written about this, and I have no great desire to add to them, save with the minor comment that paranoia about garbage-collection is still justified , albeit only in the edge-cases for most people. That said, I'll give you that Erlang GC is in many ways much, much better positioned in this regard than, oh, Java, but it still rears up and bites you in the butt when you least expect it. ( More information about Erlang's GC vis-a-vis Java here , and Jesper's truly excellent description of Erlang's GC here ).  A story from the past should serve to illustrate this. Once upon a time, in a magical land far far away - well, Her
Read more

Visualizing Prime Numbers

-
Image
From Jason Davies , we have El Patron de Los Primos , probably one of the coolest prime number visualizer that I've seen.  For every Natural number, he draws a periodic curve that intersects at that number and each of its multiples.  Needless to say, prime numbers are touched by only two curves (itself and 1 ). You can scroll to the right, and move up the prime food change. (The image above is a screen grab.  Go here to see the actual thing)
Read more

Its time to call Bullshit on "Technical Debt"

-
Image
Seriously. You know what " Technical Debt " is, right? Ok, heres the (official?) Wikipedia definition   Technical debt   (also known as   design debt   or   code debt ) is a   neologistic   metaphor referring to the eventual consequences of poor or evolving   software architecture   and   software development   within a   codebase . The debt can be thought of as work that needs to be done before a particular job can be considered complete. As a change is started on a codebase, there is often the need to make other coordinated changes at the same time in other parts of the codebase or documentation. The other required, but uncompleted changes, are considered debt that must be paid at some point in the future. And in this - somewhat purist - sense, " Technical Debt " is absolutely valid. The problem arises in the way it is almost invariably used, viz., as an excuse to not do something. Herewith a simple exercise - the next time you hear someone cite &quo
Read more