Kartik Agaram

"An opposing view: "Code you can reason about is better than code you can't. Rely on libraries written and tested by other smart people to reduce the insane quantity of stuff you have to understand. If you don't get how to test that your merge function is associative, commutative, and idempotent, maybe you shouldn't be writing your own CRDTs just yet. Implementing two-phase commit on top of your database may be a warning sign." http://aphyr.com/posts/286-cal..." - Kartik Agaram

"The first four bullets are really just different implications of the same rationale, and I'm not sure I buy that avoiding spaces or requiring capitals has any affect on converging the vocabulary. CamelCase is very common in programming, for example, and the vast majority of codebases never converge :) It seems pretty weird to suggest that Java makes for better code than C because it uses camel-case rather than underscores. Convergence requires discipline and gradual cultivation; no naming convention will get around that. (And it's fine for 'outlying regions' to never converge; they drive the engine of creativity that cultivates the center.) The fifth bullet is valid. But it's not always a huge factor." - Kartik Agaram

"Gregor Kiczales put this far better in '92: http://www2.parc.com/csl/group... (especially the Summary at the end)." - Kartik Agaram

"Perhaps the different kinds of comments are meant for readers with different levels of motivation? http://alistair.cockburn.us/Sh..." - Kartik Agaram

"When people delete a key like this, is the money destroyed from the bitcoin economy? Is the asymptotic size now 21 million less 90 BTC?" - Kartik Agaram

"Case study: http://jefferai.org/2013/03/24..." - Kartik Agaram

"That's a good question. I'm not sure, but I just thought of the idea of giving tags profiles like wiki pages, so the community could arrive at a consensus on what each tag is suitable for." - Kartik Agaram

"Thanks! You raise an interesting point about coupling. Codebases without information hiding are paradoxically more likely to be loosely coupled than going through contortions to play to a fixed interface. Another way to look at it: designing and software organizing software is hard enough to do right. Minimizing impedance mismatch between pieces gives us half a chance of focussing on the actual problem of loose coupling." - Kartik Agaram

"A similar map: http://fakeisthenewreal.org/re..." - Kartik Agaram

"Me too, but that's because of the size of the 'community' at the frontpage. Back when reddit was far smaller we didn't need subreddits because the community at the frontpage was cohesive enough to provide a nice experience. Hubski's still in that phase, but with one difference: as it grows it would like to keep the frontpage as useful as ever. With subreddits we try to recreate that sense of cohesion. But they're just one possible solution. When communities grow too unwieldy somebody has to make the explicit choice to fork a new subreddit. What if members could instead continually refine what their community was? Then you wouldn't need a centralized decision to bud off a new subreddit. You'd also be able to adapt to shrinking numbers by coalescing communities when it turns out a subreddit wasn't actually large enough to be viable in the long term. The implementation of subreddits makes these kinds of group action less convenient. *(Disclosure: I help build hubski.)*" - Kartik Agaram

""Dull and safe may not be the same thing, but they sure feel like it after a while." -- https://www.nsfwcorp.com/dispa..." - Kartik Agaram