3 ms·
Worst naming convention I've ever seen. Did they just draw from a hat of cooky names? What ever happened to the concept of choosing names relevant to the th
by um_ya 7y ago
Worst naming convention I've ever seen.
Did they just draw from a hat of cooky names?
What ever happened to the concept of choosing names relevant to the thing you're describing?
I start to understand what's going on, then they throw words like "Hoon" and "Arvo" at me, and now I'm confused again.
I still don't understand what it does, but now I don't care.
- huevo5050 7y agoFrom https://urbit.org/blog/a-founders-farewell/ 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 7y agoAnyone else ever work on a project without a firm definition? Anyone ever finish those projects?