logoalt Hacker News

mrandishtoday at 5:19 AM1 replyview on HN

Ladyada mentions in the current top post of this thread that they've reached out to the Flux.ai founder to hopefully discuss a mutually satisfactory resolution.

Unilaterally publishing Flux's demand letter probably isn't prohibited but doing so prior to discussion or any notice IS a signal. And it's a signal that could be interpreted by Flux as non-constructive, escalation or possibly even combative. In the absence of clear communication, things can be interpreted incorrectly.

I've been in far too many of these potentially contentious, early-lawyer-letter loops over the decades. It's actually shocking how easily things can spiral into unintended escalation over essentially nothing, especially very early on. And the more things start amping up, even if only in one party's imagination, it's absurd how hard to can be to climb back down. Especially with lawyers in the loop who are incentivized to fully preserve all their client's rights, posture aggressively for tactical position and burn retainer 12 minutes at a time.

I finally started to "get it" after maybe the third time in three years where I discovered after several months, $15,000 and a bunch of stress that the whole stupid thing could have been sorted in the first week by acting slowly, dismissing my assumptions and resisting all my instincts about how to respond. Let's just give these folks a week to see if there's a way to hit CTRL+Z, before we start demanding details just so we can pass meaningless mob judgement on who's right or wrong.


Replies

otterleytoday at 6:27 AM

I don’t disagree with you, but if we’re talking about the wisest course of action here—assuming what you’re saying is true—it would be to resolve the matter privately and abstain from publishing this blog post in the first place. Perhaps publishing the letter is an escalation, but so is this. It’s just passive aggressive.

show 1 reply