Go Code Review — Senior Eyes On It

You wrote it. It works. But something feels off — and your team's reviews are too polite to tell you what.

Send me up to 300 lines of Go (a service, a package, a tricky function) and we'll spend 60 minutes going through it line by line. I'll tell you what I'd flag in a real review at a senior level: idiomatic issues, hidden bugs, scalability concerns, naming, error handling, the works.

You'll leave with:

• A prioritized list of what to fix, what to consider, what's already great
• Concrete refactor suggestions (not just "this could be cleaner")
• The reasoning behind every callout — so the next 300 lines you write are better

Best for: Devs who want to level up faster than tutorials allow. Open source maintainers. Anyone whose team doesn't have a senior Go engineer to learn from.