I wonder why there are no programming checklists Lots of fields use checklists. I've never read or heard of anyone using checklists for programming. Linters resemble checklists, but they aren't a proper substitute. Linters can only cover things that can be automatically detected. That's
I'm noticing two ways of relating to an experience: 1. Experience as Content. I liked that, it was good. I didn't like that, it was bad. I didn't care about that. I was bored. 2. Experience as Prompt. What did that remind me of?
I have a hierarchy of note directories containing text files and I want to know how many words I wrote. I just put together a command to count words with Powershell. Here's what it looks like: $i=0; foreach ($item in gci E:\path\to\notes -Name '
A quick reference for tkinter: 1. window = Tk() to set up the window. 2. widget = Widget(master=window) to set up a widget in the window. 3. widget.pack() to add the widget to the window. Note there is no way to temporarily hide a widget without removing it; instead,
Ambivalence, wanting and not-wanting. What is it good for? Absolutely nothing. Sitting with? If it lasts too long I end up doing nothing. Is that a necessary feature of the experience? Huh, I guess not. I guess I could feel the ambivalence and do something anyway. But what on earth