News for hackers. Stuff that matters.
Re:Formalizing US Tax Code (Using Lean) by djoldman on Saturday November 14, 2026 @01:58PM (#50499732)
> And also, it's important to remember that in tax matters, the final arbiter of interpretation is a judge. Judges are humans, not machines. You can't "Trick" them by saying "well technically this is allowed!". Because they rule on the sprit of the law, not as it was written. Judges aren't amused when you try to be cute with how you interpret a law. And some Judges have biases, where you get a different ruling depending on if you play at their golf club or not.

> Laws aren't computer code. They are vague on purpose.

Yes... but. Tax law is a bit different because it is similar to an equation: you put in your inputs and you get your outputs.

There have been famous cases where the courts have said in essence, "yes you completely and exactly and precisely followed the law, but we're not going to allow you to do that anyway." Those rulings have become less frequent.

Re:Formalizing US Tax Code (Using Lean) by pylua on Saturday November 14, 2026 @02:40PM (#50500077)
The fact that you need a judge to tell you if what you did was wrong is indicative of a flawed system
Re:Formalizing US Tax Code (Using Lean) by jaza on Saturday November 14, 2026 @03:48PM (#50500665)
No it is not a flawed system. That is literally the legal system at work (at least the Westminster / US systems with judge-developed case law). Legislature writes the law, and nobody knows for sure what constitutes "complying with or being in breach of that law" until judiciary rules on it (sometimes decades later!).
Re:Formalizing US Tax Code (Using Lean) by pylua on Sunday November 15, 2026 @01:16AM (#50504460)
If that can’t be determined from the text is that not a problem ?

I’m not saying judges are useless but a system that operates in a less clear way only favors those with money and influence