Long-term guidance for database specialists who want to work with confidence
"Databases don't fail randomly — they fail predictably. Learning to read those patterns takes time and good company."
Working with PostgreSQL, Oracle, and MySQL in production environments since 2011. Focuses on performance tuning, replication architecture, and backup reliability.
"Before, I'd spend half a day diagnosing a slow query. Now I have a systematic approach and I know where to look first. That shift didn't happen overnight — it took about four months of regular sessions."
Structured work, not scattered advice
Hesbo Jundal started in 2019 with a single premise: generic database courses leave too much out. They teach syntax but skip the judgment calls — when to denormalize, when an index actually hurts more than it helps, what a 200ms spike in I/O wait actually means at 3am.
Mentorship here is a working relationship, not a subscription to content. Every month you and your mentor review real database environments — yours, or case studies from comparable production systems.
Sessions happen weekly by default, with async support between meetings via shared notes and query logs. Progress is measured by what you can diagnose and resolve independently — not by modules completed.
Reading EXPLAIN ANALYZE output, identifying plan regressions, and working with statistics — session by session.
Testing restore procedures, validating point-in-time recovery, and building runbooks you'll actually use under pressure.
Managing migrations on live systems without downtime — reviewing real ALTER TABLE risks and online schema change tooling.
Setting up pgBadger, slow query logs, and alerting thresholds so you catch problems before users do.
Questions about the program or how sessions are structured?
Get in touch