Hacker News new | ask | show | jobs
by f0e4c2f7 1613 days ago
This is heavily weighted towards computing / programing.

Roughly:

1: Find out what fixed looks like. When did it stop working? Has it ever worked?

2: Form theories about why it may not be working (googling is part of forming theories)

3: Pick what you consider to be the most likely problem, or the fastest theory to test.

4: Test the theory (May require googling to figure out a falsifiable way to test)

5: if that was not the problem, consider if your test falsified any more theories or changed the liklihood of other, then move on to the next test

6: Repeat until you're out of testable theories.

7: Come up with more testable theories (if you already tried everything you could think of and google, start asking people online and reading books about the problem.)

8: Keep testing theories.

9: Fix the problem.

10: Celebrate.

1 comments

10. might be a commonly overlooked step for some people. It's probably not very helpful for the just fixed problem, but it will be for the next occurring thing. Resonating about what was and feeling good about it increases self-efficacy/-confidence/-assurance, which is important for the future. Keep it up!