Mistakes
by @nacin
THE ONES I HAVEN’T ERASED FROM MEMORY, AT LEAST
“Working on old code is like
stepping back in time... to a time when I sucked.”
— @kevinmontrose
Not leaving myself breadcrumbs.
Useful notes and comments are a good start.
Theme Name: WordPress Default Theme URI: http://wordpress.org/
Worse, not renaming my imposter theme.
Not using child themes.
Boost my ugly code’s self-esteem.
Whitespace. It’s why you can read this sentence.
November 16, 2009
Next time, find ways to get involved earlier.
“I’m reclassifying this as a defect in
the UI flow.”
[ Type changed from enhancement to bug ]
Older posts are next. Newer posts
are previous. Got it?
I know, I’ll just write
_______________ (thing that WP already does)
Using the Theme Editor
It’s nice and all, but…
Trying WordPress MU
before knowing anything about WordPress
Tying installs together with gum
blogs.example.com/here blogs.example.com/there
blogs.example.com/everywhere
Not escaping, sanitizing, or
validating Security is tough,
but it’s not optional.
“One word, capitalize the P.”
I swear, every wrong instance was a typo.
Habits I haz them.
a
M
T
W
T
F
S
S
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
ZERO
21
M
T
W
T
F
S
S
ZERO
25
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
#blamenacin (Thanks, Pete!)
Learn more at the core development
workshop tomorrow
Recommended
