Juan Carlos Gutiérrez Huérfano

I spent four years building enterprise systems in Java and Spring Boot, most recently as a Software Architect, and I write TypeScript backends with Node and NestJS. I build Actors the way I build production services: a schema you can rely on, errors you can read, and documentation that tells you what the tool does not do.

What I care about in a data Actor

• A stable schema. Field names and types do not change under you between runs.
• Honest nulls. If a source does not publish a value, you get null — not a guess dressed up as data.
• No personal data. My Actors read company and public technical sources only. No profiles, no contact scraping, no lead databases.
• Readable failures. Every run writes a summary of what was fetched, what failed and why.

If something breaks or a field would be more useful in a different shape, open an issue on the Actor — I read them.