When we started a few months ago with Dap we also decided to create a journal. This journal. One post every week, everyone can contribute. We had a lot to share, not only about what we are building but also how. The process, the impacts, the risks, the issues, etc. We started writing one post, two posts, and so on. Then I went and read someone else's blog and I started noticing a pattern (I'm not a genius, don't worry). You could even know which model was being used behind to write it. Even with flavors, you could tell.

So I decided to write this one myself. And I hope you can notice :)

AI is great, is helpful and every day it passes by I get more amazed, and even stressful as it is to us (software engineers) I kind of feel grateful from being part of this transition. I have a way to express my creativity and my abilities in a way that wasn't possible before. But there is one thing to this transition that is more fundamental, something that we can't measure. Trust. It is part of the human nature and even if you "trust" the AI to help you to do things, to give you ideas, etc. let me tell you, you don't really fully trust it. You may "trust" Opus, but do you trust Anthropic... really? I don't. Sorry. Do you trust that agent doing a bunch of changes overnight that changed 30 files and landed it with another AI approval? Hell no.

I can write here and tell you more about how Dap solves that. That's the main goal of this journal, but I'll take a quick detour here. Trust is something we can't measure, right? And everything that we build into Dap comes with the mindset to overcome that: build agents and use AI in a way that you can trust — that's one of best values I realized. Dap is not just another off-the-shelf product. It is us. The team behind. The humans building, alongside a product, the trust and accountability that we need for this transition.

That's the most important piece to Dap. Crunchloop.