jpcapdevila

Awesome, I love this .cpp trend! Thanks for your work!!

From the readme this may be interesting:

Event-based: if you can track it, you can charge for it;

I see this being useful for usage based pricing.

I think it is ok for you to post as long as you are straight forward about the equity only compensation and follow the post format ofc.

Not a moderator, but as a reader I would not mind.

Edit: typo

I think what you have experienced is very real. Code (and most forms of expression) are a way to externalize your state of mind.

I've seen it with my own emotional states but also with coworkers when they are going trough a rough time.

This is also why it is difficult to understand others ppl code. And it gets easier as you build a relation/get to know them better. The better you know someone, the easier and faster you can understand their code.

I feel like that is why coding standards, code reviews etc make a codebase more maintainable. You strip the code emotions away or at least reset it to a common level across the team.

This really resonates with me, I like the idea if product as container for emotions.

But I think the author misses one point here:

> I believe the real skill in making products isn’t some “making products” skill, but rather a skill in feeling your own subtle emotions.

I believe there are high emotional, highly empathetic people that can talk to other people, understand their emotions and create something for them.

This for me would be "making products skill". This is how you create products for things that you can't experience yourself directly.

Here's a bet, in 5 years every major cloud provider will offer SQLite.

Specially the edge providers (official SQLite for wasm in the works.

Because the operational simplicity most developers will choose it for new apps.