Hacker News Reader

Comment by vlovich123 | Hacker News Reader

Or they’re saying this because they know the IRS effort doesn’t have competent people on it (think what happened with the healthcare website when it launched) and is just prepping the waters for a “see we were telling you along this was a bad idea” criticism for congress people to spike it later. It’s really hard to intuit the strategy being employed so best to just ignore them altogether. And if this turns into a partisan issue at all (which an unclean launch might because people are dumb about government tech in the US), then expect the Trump administration to kill this if they win to prevent this from becoming entrenched and popular like Obamacare is.

View on HN

I've used the US Free File Federal Taxes for the last five years and it just wasn't a problem, and I have yet to see anything that looked like programmer incompetence.

Now, that said, the way you debug your submittal is to paste an entire page of error gibberish that looks like very low level database error output into an entry box they point you to. Sounds gross! Ewwwww! Well actually I've been debugging c++ templates since forever and hohum it doesn't bother me. However... every single time it decoded the problem and told me exactly what I needed to do. It has taken me 2-4 tries each year to get it debugged and then it sails right through. The final result I've fed into two different state forms and that has sailed right through too. All free, and not that much of my time.

Now if they can get the UI for normies painless, which I suspect is the main programming problem (I don't say that UI programming is trivial), this will take off like a rocket ship and the US can the join the coterie of civilized nations that do this for all their citizens.

If you're referring to Free Fillable Forms, the error messages are not DB errors, but "business logic rules errors". They do look like gibberish, but buried inside them is a code that can generally give a pretty clue as to the error.

I agree that it would be much nicer if they said "The amount of line 29 of Form ABCD does not appear at line 18 of Form WXYZ".

Even nicer if you never had to manually transfer amounts between forms.

Oh yes I am sorry; I didn't mean to imply that I thought that the DB was throwing an error. What the filing process email message body stated looked something like approximately "Form line xxx violates schema requirement such and such: <more gibberish>".

I was thinking when I scanned the message was that I bet I could reverse engineer the problem from this back end generated text but why not do what the instructions say and just feed it into the parser box? And every time the next email message gave me exactly the thing I needed to do. It was cool, for a weird sort of nerd.

So no, I was casting shade where the process was right in the sunlight: I made the mistake, and the business logic caught it, and told me correctly every time what I needed to do to fix it. I liked the whole process a lot.

Yeah, me too! Been using FFF for about 8 years now.

Reply on news.ycombinator.com