A lot of complexity in the tax code comes it using a mishmash of type systems. Why is it hard calculating what someone's income tax is? Well, when you dig into it, income isn't an integer. It's an arbitrary object which can support a stupidly high number of interfaces.
-
-
Object relationships, where to start. An LLC can be shareholder in a corporation which is a shareholder in a corporation which is a member of an LLC which is a member of the first LLC in this sentence.
Show this thread -
One of the benefits of Atlas is, while working within a structure which exists in the world, we get to make some simplifying assumptions by fiat. For example: all Atlas companies, at present, are Delaware C corps. That reduces dimensionality by a factor of over 100.
Show this thread -
So when we're building a tax product, or working with accountants and telling them to write procedures for working with thousands of Atlas companies, we can bake in the knowledge that we only have to address the complexity possible in Atlas companies, not in the untyped world.
Show this thread -
As of the day when we started Atlas, we just created Delaware C corps. Over time, the hope is that "an Atlas company" implements the interface "Delaware C corp" (or similar) where you need that to plug into legacy infrastructure, but is transformatively better.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.