Skip to content

Commit d4ce0ba

Browse files
committed
Aesthetic improvements
1 parent 89fcc7e commit d4ce0ba

File tree

2 files changed

+11
-8
lines changed

2 files changed

+11
-8
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
# The Debugging Checklist
22

33
Look at one of the checklists provided above that pertains to your particular debugging woes. Maybe they can help.
4-
Please fork and improve as you see fit!
4+
5+
**Please fork and improve as you see fit!**

web-debug.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,28 @@
1-
# Web Debugging Checklist
1+
## Web Debugging Checklist
22

3-
1. Blame yourself.
3+
1. **Blame yourself.**
44
* In debugging, having an ego will only cause you to work longer and harder to solve a bug. Be humble; accept your humanity. Make 100% sure that the way you're attacking a problem is _actually_ isolating the problem.
5-
2. Blame your tools.
5+
2. **Blame your tools.**
66
* Have you got cache enabled? Are you working in IE6? Try to ensure that your tools aren't giving you false-positives or false-negatives. Use an HTTP proxy like [Charles Proxy](http://www.charlesproxy.com/) to debug HTTP requests.
7-
3. Blame your framework.
7+
3. **Blame your framework.**
88
* Are you working with a framework or library of some kind?
99
* Are you sure it's not manipulating the results or getting in your way?
10-
4. Blame your environment.
10+
4. **Blame your environment.**
1111
* Is your server configured the way you need it to be?
1212
* Are you running the write version of the software you need?
1313
* Could another piece of software be getting in the way?
1414
* Be sure to disable any caching technologies to ensure you're always looking at the most recent data, and that your _actual_ code is executing every time (not some cached version).
1515
* Have you tried turning it off & on again? =)
16-
5. Blame your language.
16+
5. **Blame your language.**
1717
* Is the code you're debugging very complex or novel? Maybe it's a bug (highly unlikely)
1818
* Always break the problem down into as small a piece as you can - it's probably you
19-
6. Blame the world.
19+
6. **Blame the world.**
2020
* Have you tried logging a bug?
2121
* Have you tried asking a question on [Stack Overflow](http://stackoverflow.com)?
2222
* Have you asked a friend? Sometimes speaking the problem out loud can give you insight into the problem at hand.
2323

24+
---
25+
2426
## General Considerations ##
2527

2628
* **ALWAYS** check your premises. Assuming makes you an ass.

0 commit comments

Comments
 (0)