984
you are viewing a single comment's thread
view the rest of the comments
[-] barrage4u@lemmy.world 47 points 1 year ago

This is why I write down the questions I'm trying to answer in a text doc, e.g:

Where is this network call comming from? ../some-api-call.js Why do you think it's causing a 403?

  • I am authenticating correctly
  • the object seems to exist in s3
  • the bucket name is wrong

Etc. So if I lose my thought (all the time), I know exactly what and why I was doing it. Also stops you from re-investigating things you forget

[-] SeriousBug@infosec.pub 4 points 1 year ago

It's also an amazing way of duck-debugging. By the time you write down what the problem is, you'll figure out where's the issue or at least what you should try next.

"X is giving me an error, I checked X's logs. X communicates with Y... Oh, I need to check Y next!"

And if you can't figure it out, you have the problem and everything you tried documented so you can ask for help and get answers effectively.

load more comments (2 replies)
this post was submitted on 07 Jul 2023
984 points (98.0% liked)

Programmer Humor

32503 readers
419 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS