Every argument clarity score on this site is built from rows on this page. Each
question and answer was assessed with names hidden, the host's own answers included, on
four things from 1 to 5:
directness (does it answer the question asked), coherence (do the ideas follow),
precision (concrete details and clear references), compression (says a lot per word). The weighted
mix (30/30/25/15) is the exchange score. A person's published score averages their exchange
scores on raw tape only, at least 8 of them, shrunk toward the cohort mean.
Full method →
Answered produced feed
D 5 · C 5 · P 5 · Cm 4 4.85
Q What was that process like? How'd you find the right, right folks?
A So in one sense, we, we had the good timing that ARKit just got launched at that time. I mean, that's another funny story when it got launched. So there was a lot of positive enthusiasm for the space around that. That was one. The other one, we were lucky to really get connected with investors that really believe in this future and with us that it would take a long time. So we got, um, backed up, our lead, Investor for our seed run was, uh, Jeff Clavier from, um, Uncork Capital, who really was with us in really believing where all these pieces were coming about and, and really taking that bet on us. And besides that, it was also Founders Fund, also seeing that vision with us that, yes, this makes sense. So it's kind of finding those, those kind of people.
AI assessment note: “our lead, Investor for our seed run was, uh, Jeff Clavier from, um, Uncork Capital”
Answered produced feed
D 5 · C 5 · P 5 · Cm 4 4.85
Q work on a small team of four, um, where everyone kind of knows everything, um, and everyone, everything is in everyone's heads versus a team of 30 or 50 or for some of us, you know, hundreds, um, that is very different. So, uh, you kind of constantly need to be assessing is this style of working or this methodology, um, is this right for this stage of the company?
A Yeah, I think the point of evolving the process is something we've been, ah, doing a lot. So back when we were at Escher, we were only with four engineers and me building the product. So back then, ah, it was very messy. We're just trying to move as fast as possible, really, so zero documentation. Everything was kind of whiteboards, and everyone kind of could, ah, handle everything in their heads and, and build it out. And in terms of, we didn't really do sprints, because I think that some engineers didn't quite like it as much. And there were just too many big tasks, and we just trusted different individuals to go and tackle kind of one area, and then we would integrate it. But now, things are very different. As we hired, I think the team has tripled already in the past eight months for, for, for the AR platform product. When you have a bigger team, you definitely need a lot more process to be able to be efficient and communicate, because you don't want to duplicate, and not everyone knows everything, and The system grows in a lot of complexity. So we went from zero documentation to a lot more. We went from, we used to have a little CI, but now is, um, very much of a CI that actually builds to all the architectural flavors to Linux, Mac OS, Android, XSX, Android Arm, iOS, et cetera, and actually runs all the tests in all of them, and actually catches a lot of the bugs, and we …
AI assessment note: “the point of evolving the process is something we've been, ah, doing a lot”
Answered produced feed
D 4 · C 5 · P 4 · Cm 4 4.30
Q And so obviously like Niantic, you're working on games. Um, at what point do you think AR becomes this kind of like first class citizen in media, you know, alongside video, photo, I guess audio?
A Yeah, I think it will, um, it will take time, because we're at the early stages. I think the progress of, um, technology has, like, different cycles. I mean, if you read some of the work by, um, like, Carlota Perez, who's an economist, talking about innovation cycles, there's, like, big two stages. Stage number one is when technology gets installed. Quote, unquote. Uh, so installation types of technologies are when the applications are not ready to be built because you really need the tooling to be able to express those applications, and examples of types of installation types of technologies are just like network infrastructure, operating systems, uh, programming languages, all these levels of abstractions that are needed because you're not going to, let's say an example, today it would be crazy to program a website based on assembly, right?
AI assessment note: “it will take time, because we're at the early stages.”
