Exploration Through Example

Example-driven development, Agile testing, context-driven testing, Agile programming, Ruby, and other things of interest to Brian Marick
191.8 167.2 186.2 183.6 184.0 183.2 184.6

Tue, 25 Apr 2006

Raise my taxes, please

I don't know what the US should do in Iraq. I believe we're morally obligated to make it come out the best we can. I don't know if we're now doing that, if we could do better by changing course, or if our presence irretrievably does more harm than good. Since the Administration is unwilling to be truthful with the citizenry, since the press is unable to travel in Iraq and is in any case broken as an institution, and since I'm certainly not competent to collect and judge the data myself, I expect I won't know for twenty years, if ever.

However, it is wrong for me to sit here, fat and happy, paying no price while Iraqis, the US military, the UK military, and their families suffer. The least I can do is not add to the trouble of others by expecting my children to pay for all this.

Using figures from the US Internal Revenue service and the Congressional Research Service, I figure my family's share of the Iraq+Afghanistan wars to date is around US$2749, and our share of ongoing costs is US$630 per year. Since we are a two-income family, make rather more than the average, and I believe in a progressive income tax, my rough guess is that we should pay a lump sum somewhere between US$5000 and US$7500, and then between US$1000 and US$1500 yearly. I urge the Congress to raise my taxes accordingly.

I'm serious. Who's with me?

Calculations based on 131,301,697 individual returns (2004), US$6.9 billion per month cost of operations and US$361 billion spent to date (October 2005).

I believe in a progressive income tax because a dollar is worth less to me than to someone who makes minimum wage.

## Posted at 07:25 in category /misc [permalink] [top]

About Brian Marick
I consult mainly on Agile software development, with a special focus on how testing fits in.

Contact me here: marick@exampler.com.




Agile Testing Directions
Tests and examples
Technology-facing programmer support
Business-facing team support
Business-facing product critiques
Technology-facing product critiques
Testers on agile projects

Permalink to this list


Working your way out of the automated GUI testing tarpit
  1. Three ways of writing the same test
  2. A test should deduce its setup path
  3. Convert the suite one failure at a time
  4. You should be able to get to any page in one step
  5. Extract fast tests about single pages
  6. Link checking without clicking on links
  7. Workflow tests remain GUI tests
Permalink to this list


Design-Driven Test-Driven Design
Creating a test
Making it (barely) run
Views and presenters appear
Hooking up the real GUI


Popular Articles
A roadmap for testing on an agile project: When consulting on testing in Agile projects, I like to call this plan "what I'm biased toward."

Tacit knowledge: Experts often have no theory of their work. They simply perform skillfully.

Process and personality: Every article on methodology implicitly begins "Let's talk about me."


Related Weblogs

Wayne Allen
James Bach
Laurent Bossavit
William Caputo
Mike Clark
Rachel Davies
Esther Derby
Michael Feathers
Developer Testing
Chad Fowler
Martin Fowler
Alan Francis
Elisabeth Hendrickson
Grig Gheorghiu
Andy Hunt
Ben Hyde
Ron Jeffries
Jonathan Kohl
Dave Liebreich
Jeff Patton
Bret Pettichord
Hiring Johanna Rothman
Managing Johanna Rothman
Kevin Rutherford
Christian Sepulveda
James Shore
Jeff Sutherland
Pragmatic Dave Thomas
Glenn Vanderburg
Greg Vaughn
Eugene Wallingford
Jim Weirich


Where to Find Me

Software Practice Advancement


All of 2006
All of 2005
All of 2004
All of 2003



Agile Alliance Logo