Gergely Orosz

And this is talking with like the greats of the industry who have lived through the Ken Beck, Martin Fowler, Grady Booch.

And they're all saying that they have seen change like this, like, for example, when they went from mainframes to microprocessors.

But it was throughout more like a decade, not a matter of a year or so, or maybe we're now at this point two or three years.

And they're all saying the same thing, that the change is faster.

But yeah, as you say, it's very easy to rewrite history and say it was always obvious, but it's just hard to tell.

So far with OpenCode, especially with OpenCode, you and the team have reached really good success.

What are the things that comes to building products and your engineering principles that have not really changed from the early days or the ones that you've learned and you've stuck to them and it helped make OpenCode successful as well?

What has helped you there?

What has helped you to get this product sense better or figuring out?

Because it sounds like we talked a lot about thinking, about reflecting, about having one elegant solution that can solve multiple seemingly unrelated problems.

Can you...

Let us in a little bit of how the OpenCode team today works.

Like, tell us how many people there are, what kind of setup.

And maybe we can walk a recent feature that you or someone else launched or, like, was it even a team?

And then how you also get this, like, immediate feedback.

One thing that comes up, we didn't mention it a single time in this conversation, but elsewhere it often comes up, is taste.

There's this notion or idea that one thing that AI is just very bad at and probably will stay bad at is having taste.

And how as engineers, taste, taste, product sense, they're, I think, synonyms to some extent.

In fact, I've even heard that Microsoft generally has a training for taste to get better at taste, which I'd love to see that one.

What is your take on taste as a whole, as a concept?