2,362 karma · joined March 7, 2008
email: lincoln/techhouse.org
Others in this thread have said that there are leadership issues currently, leading to some kind of stagnation or decline. You said in another comment that Paolo was controlling in terms of the vision, and it needed multiple visions to succeed.
1) Can you expand on that? i.e., what would it take for Arcosanti to have succeeded? Just Paolo letting people run with it?
2) What, if anything, would it take to "revive" Arcosanti today? Money? Visionaries? Kicking people out?
3) Why did you live there? Why did you leave? Any interesting stories?
One subtle thing which I noticed is the distinction between class patterns and name patterns (bindings). In particular, it is possibly confusing that the code `case Point:` matches anything and binds it to the value Point, whereas `case Point():` checks if the thing is an instance of Point and doesn’t bind anything.
At such a retreat, you should expect to give up technology and live according to Buddhist precepts for 10 days, and one of the major claims of meditation is that it will help you unlearn bad habits related to focus and distractions, which can be carried back to the world with you once you complete the retreat.
Most of today’s media tends to “tell you what to think” in advance of reading the story, and I would argue that is a big piece of the (poorly defined) problems with society today.
I’m glad you wrote your comment, because it helped me realize why it’s worthwhile to me to have this sort of article posted on HN — I think it’s a valuable skill, to figure out what to think (instead of being told it upfront).
I think the way most investors do it is probably by maintaining a “story” about how the world will change that most people haven’t realized, and then matching that story up with ideas they hear.
I’m not sure if there is a more robust or rational approach that actually works. The ideal investment plan would evaluate each idea/“potential market” on the expected value of market size, averaging various plausible scenarios according to their probabilities. But I don’t think many people can run a process like that without injecting a ton of priors about how the world will evolve... it all seems to devolve into an argument over which macro trends matter in the next 10 years or so.
For example, "we are egolessly mission driven" is one of our values: this helps us recruit the right people (drawing people want to work at a mission-oriented company; turning away people who just want a random job), as well as helping us notice and nudge employees who might be (accidentally) engaging in political maneuvering.
"we focus ruthlessly on the most important thing" helps us filter recruits out who don't want to take work seriously, helps make our Slack channels much quieter / less spammy than most companies, and helps employees self-improve along the axis of protecting their focus time.
Stating explicitly what you care about, and talking about these things a lot, is a huge aspect of how a company defines its culture as it grows beyond ~ 10 people or so.
I only really took away one thing from the book (some deeper level of understanding of what is meant by "quality", in the sense of craftsmanship). I value that understanding and am happy I read the book, but I don't use that wisdom very often in my life.
Maybe you're reading it in a way which expects it to have a plot? I don't know, I think book recs are generally hard and people should only trust book recommendations from people who like books for the same reasons.
The project is not easy. It requires carefully reading tax codes and implementing them, handling presumably thousands of explicit legal requirements plus whatever edge cases exist that may or may not be explicit in the law. Not to mention keeping up with annual changes. If you screw it up, whether or not you are legally liable, people are probably coming after you anyway. And the support nightmare...
That said, I think a programming-languages approach might be a good one to try to execute on this. Keeping the source code as close to the tax code as possible seems the only way to stay sane with respect to long-term maintenance.
If the design appeals to you I do still recommend it despite not preferring it myself. The build quality was great. I don't have any comments in particular about the height, not something I noticed.
I'm not fully sure what you are asking -- I would guess you're referring to the fact that it's harder than usual to type with one hand and mouse with the other, because you have to reach across to the other side of the keyboard?
If that's what you're asking, I agree -- but I consider it a good thing :). I found that the kinesis helped me focus on touch-typing more and relying more on keyboard shortcuts to navigate; it's a bit of a learning curve but ultimately worth it for ergonomics and speed.
https://www.lesswrong.com/posts/X2AD2LgtKgkRNPj2a/privilegin...
In short, it does seem like it should be illegal to pull names out of a hat.
Also, black coffee for me helps suppress my appetite.