Bernardo Secades
Backend engineer — Go & distributed systems. I build with AI in production and write about what actually works.
Software engineer building backend microservices in Go. I focus on distributed systems: service boundaries, event-driven communication, and finding the right balance between simplicity and resilience.
I have Claude Code wired into my daily workflow — it's open whenever I code. I use it for reasoning through service designs, catching subtle edge cases during code review, drafting migration plans, and speeding up the boilerplate-heavy parts of Go so I can spend more time on the interesting constraints.
Beyond personal use, I've been working on cross-team adoption: sharing patterns that work, running demos, and building shared conventions so the whole team can get consistent value out of AI-assisted development without each person reinventing the wheel.
How a per-team plugin marketplace stopped Claude skill duplication across teams
Three teams, three incompatible ways of sharing Claude skills, zero reuse. A per-team plugin marketplace fixed it — here's the layout, the template, and what it actually changed.
MCP: when it's worth it, when the CLI wins (the GitHub case)
The GitHub MCP ships around forty tools you mostly won't touch. If you have a shell and `gh`, the CLI does the same job with one tool instead of forty. MCP still earns its place — just not here. Here's the decision rule.
Claude Code: one workspace for many repos
Launch Claude in the parent of your repos so cross-service tickets stop being N isolated sessions — and let a workspace-level CLAUDE.md describe how the pieces connect.