Trying to actually explain why you do things is always a great way to figure out that in fact, you DON'T have a good reason! For best results, write clearly and revise. As good writing teachers repeat, good writing is good thinking!
-
Show this thread
-
Paper writers see this all the time — but does it happen to programmers when documenting code or writing design docs? I'm sure it must happen (if not, why not?), but can't recall examples there, while this just happened to me again during paper writing.
3 replies 0 retweets 7 likesShow this thread
Replying to @Blaisorblade
Writing articles about ASDF made me improve it significantly: having to explain one obscure part of the API was costlier than simplifying it away. Especially if it was obscure enough that no one (in Quicklisp or on the mailing list) seemed to rely on the historical behavior.
1:35 PM - 8 Jul 2018
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!