|
|
|
|
|
by ryandrake
1118 days ago
|
|
I've argued in the past here on HN that your first employee should probably be an attorney--or at the very least have one on retainer, and got absolutely roasted for it. I still believe it though. How do you even know if your software product is legal everywhere you plan to distribute it? Are there any states that forbid what you are doing? Are all your dependency licenses really compatible? Are your logging practices legal in the EU? A single lawyer is not going to be a deep expert in Polish law, but he or she will be able to at least give general advice to keep the product from being dead on day one. We laugh-complain about "ha ha the lawyers are designing our products now" but it kind of has to be the case in the complex legal environment businesses operate in. |
|
500 have a team that looks like 3x developer, a design person, and a sales person.
500 have a team that is like 1x developer and a Lawyer
Which one wins? Which hits market first? Which is more successful?
An early company has to spend money on the core product. If you get wacked by a lawsuit and shut down in year 2, it's a cost of doing business and you go do something else.
There isn't enough time in the day or money for an early startup to get every single law perfect.
So to answer the OP: You just do your best, and correct when you screw up.