←back to thread

On Building Git for Lawyers

(jordanbryan.substack.com)
162 points jpbryan | 1 comments | 14 Nov 24 15:48 UTC | HN request time: 0.567s | source
Show context
renewiltord ◴[14 Nov 24 16:47 UTC] No.42138055[source]▶
Juro was this. I used it for redlining a few times but it didn’t work because the other guy has to be onboarded onto the system.

Unscrupulous opponents will turn off Track Changes in MS Word to catch you off guard.

replies(1): >>42139174 #
1. kevin-oconnell ◴[14 Nov 24 18:07 UTC] No.42139174[source]▶
That's a great point. That's why we built it to work and add value even if the other guy has not been onboarded onto the system. This made the engineering lift way bigger, because the system needs to be able to accept and process whatever the other guy sent you. This makes it an open-ended problem, and we needed to be able to handle any possible edge case that the other guy's docs could introduce.

Juro and others make the other guy onboard because that limits the scope of the engineering problem. You can only create what the platform lets you create, so you know in advance what the system needs to handle. This approach makes it easier to build. But the problem is that it is really hard to get the other guy to onboard. As a result, your MVP is not really an MVP.

Our approach required way, way more engineering work up front. But it put us in a position where getting the other guy to onboard is a "nice to have", not a requirement.