Course with Luca
Luca — How to Debug Code You Did Not Write
How to debug code nobody on your team wrote, 1:1 with a tutor that declines to name the cause. Four parts from a reliable reproduction to git bisect, ending when a week-two engineer can explain a real production cause in three sentences.
What you’ll master — Outcomes you can use
- One production bug found alone
- They explain a cause in three sentences
Your tutor
A backend engineer who onboards new joiners by handing them a failing service and declining to explain it.
Unhurried · Curious · Allergic to guessing
Questions about this course
How do I debug a failing service in a codebase I just joined?
How to debug code nobody on your team wrote, 1:1 with a tutor that declines to name the cause. Four parts from a reliable reproduction to git bisect, ending when a week-two engineer can explain a real production cause in three sentences.