[huevo5050]

From https://urbit.org/blog/a-founders-farewell/ :

"Urbit's internal opacity persists for two reasons, one good and one bad. The bad reason is just laziness. The good reason is justified fear of premature explanation, which like premature optimization ruins the annealing process.

When you don't know exactly what you're doing, preserve as much ambiguity as possible. For example, a name that means something is a commitment to one specific explanation; a name that means nothing is no commitment at all. A cryptic name is productive procrastination; it lets the hard problem of naming get solved later, and hence better."

[unlinked_dll]

Anyone else ever work on a project without a firm definition?

Anyone ever finish those projects?