EN
Contact — let's talk about your technical problem
Write to me if you lead something that needs technical judgment: architecture, legacy, technology sovereignty or an external tech lead. Free initial diagnosis.
Tell me what's stuck
You don't need the project fully defined: most conversations start with "we have this and we don't know where to start". If you lead a company, an organization or a technical team and the problem is complex, just write it to me as it is. The initial diagnosis is on me.
Three ways to start, depending on what you need
- A concrete problem that's blocking you? Write to me with the context (what system, what happens, what has been tried) and I'll tell you if it's my turf and where I'd start.
- Need a trusted second opinion before a big decision? Ask for a review of architecture, stack or risks before committing budget: write to me.
- Want an external tech lead or mentoring for your team? Tell me how the team is doing and what you need: cristo@duck.com.
Where to find me
- ✉️ Email (fastest): cristo@duck.com — I reply within 24–48 h on business days; if it's urgent, put it in the subject line.
- 💼 LinkedIn: linkedin.com/in/cristodcgomez for formal professional inquiries.
- 🐘 Mastodon: @cristomc@w3c.social — for open technical chat.
- 🦋 Bluesky: @cristodcgomez.dev.
- 📡 Blog RSS: cristodcgomez.dev/en/rss.xml — if you'd rather read before writing.
📍 Bergen, Norway — on-site in Bergen and Vestland, remote worldwide.