Loading…
3
A senior dev told me to read the docs before debugging, I thought it was a waste of time
I was stuck on a simple Python loop for 3 days last month, kept changing my code and breaking things more. This guy on a Discord server, he runs a small web dev shop in Austin, said to open the official docs for the library I was using. I ignored him at first because it felt slow and boring, but then I finally did it and found a one-line note about a default argument that was causing the whole mess. After that I fixed it in like 10 minutes, so now I check the docs first whenever something weird pops up. Has anyone else had a moment where reading the manual actually beat trial and error?
1 comments
Log in to join the discussion
Log In1 Comment
alice8087d ago
Three days on a loop is the kind of pain that makes you question your whole career, so I feel you. I once fought a CSS bug for a week, then found the fix in a single paragraph about z-index stacking that I'd skipped. Now I treat docs like a cheat code, it's boring but it saves me from my own dumb experiments.
3