bytes.zone
/
bytes.zone
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fix typo

main
Brian Hicks 2021-06-22 13:17:47 -05:00
parent ac3ab0a7cb
commit aef0513eff
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/posts/rule-1-simplify-when-the-program-works.md
View File

@ -32,7 +32,7 @@ Well, when I've ignored this advice, I notice I tend to start ripping out useful
I end up totally muddling my code with unrelated changes, and despite all the effort the program *still* doesn't work right.
Eventually, I've maybe made something kinda-sorta like the change I tried to make, but it's way harder for my team to review.
In my experience, I need to be in one of two modes: making changes to the make the program work, or making changes to make the code simpler.
In my experience, I need to be in one of two modes: making changes to make the program work, or making changes to make the code simpler.
"Simplify when the program works" has been helpful for me in recognizing when I need to switch!
## Avoiding Perfectionism