3 ms·
Count me as one of the people who needs to pay for software to do taxes every year...it's only something I do once a year, so not frequently enough that persona
by danso 11y ago
Count me as one of the people who needs to pay for software to do taxes every year...it's only something I do once a year, so not frequently enough that personal automation would be worthwhile (even as a weekend project)...and...the tax code to me is probably like what software installation is to the people who pay fees to Geek Squad :p
But this from the author sounds promising:
> By re-presenting the tax calculation as a tree, we have the ability to trace back what led to any surprises on the tax form, aggregate multiple users, and otherwise process the information in a manner that would be difficult or incoherent using only the form view. If your financial situation gives you the freedom to act on what-if scenarios, or if you are a tax researcher considering the situations of diverse taxpayers, the structures here are hopefully more amenable to your needs.
I mean, I guess that's the normal pattern of software innovation...take something very specific, abstract it a bit, and now you have something that opens new ways of thinking and exploring. I wasn't aware that there was XML metadata that could be interpreted...though in retrospect...obviously there would have to be for tax software to stay up to date, though I pictured in my head that Turbotax and its peers just bring in hundreds of data entry persons to pore over reams of tax code paper documents to fix up the app every year.