Skip to main content

Health Care Bill: No federal money on abortion

I haven't read the new health care bill and I probably won't read it. But from what I've heard, it specifically bares federal money from being spent on abortion. I think this is very wrong. Regardless of whether you are pro-life or pro-choice (pro-abortion is a word used only by demagogues because no one really wants more abortion) , as long as abortion is still a legal medical option, why should we specifically deny it federal funding? Sometimes I think people forget what it means to be part of a community. You don't get to pick and choose what you want your tax dollars to be spent on. Just because we all can't agree on the same policy on abortion doesn't mean we should undermine it. If every other medical option get federal funding, why shouldn't abortion? And where does it stop? Will we stop funding mental health because we think the power of prayer should suffice? Will we stop funding planned parenthood because the catholic church doesn't believe in contraception?

When someone says "I don't want my money to pay for x and y..", I feel I need to explain to the person that your tax money already pays for a lot of things you can't personally use. For the past 11 years, my tax money has been funding the education of a lot of strangers. I don't necessarily believe public money should pay for private schooling but nevertheless charter schools keep getting my state tax. I don't believe in wars and yet a lion's share of my tax dollars keeps funding 2 wars. I don't believe the military should be inducing recruits with huge sums of money and yet I can't seem to stop them!

When you pay tax, you can't pick and choose what to spend your tax money on. Unless you organize and get the offending item declared illegal. So if you think abortion is wrong, get together with people of like minds and get Roe v Wade overturned. But trying to circumvent the law by freezing funding for it is diabolical.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…