TK for Code?
I just learned while reading the “Learn about what’s new” link at the bottom of the editing page for my first Medium post, about putting “TK” into your text to stand for something that needs to be completed. This is apparently an old publishing trick that helps you get your writing done without looking up every little thing that you don’t yet know in enough detail to write about it. I Googled it, of course, and found The Two Letters that Will Help You Write Faster. Nice idea. And when there’s a “TK” in a paragraph, Medium puts a little yellow “TK” to the let of the beginning of that paragraph. Cool.
I write code for a living. TK for code is a function that isn’t written yet, usually with a body that signals an error. I usually put some sort of comment in such a function, and I don’t tend to leave many of them unwritten for long. I suppose I could start doing so, and leave some standard comment that would be easy to grep for. But I probably won’t. I tend to think about code top down and implement it bottom up, testing the low-level stuff before trying to run the higher-level stuff. Running into random TKs in the process wouldn’t be fun.
I’m typing this on my 27" iMac, a machine I sit in front of all day every weekday, and for at least a few hours on Saturday and Sunday, more if I’m in the middle of something exciting. The Medium text editor is really good. It’s a joy to use. I doubt I’ll switch all my tech blogging from lisplog.org, but I might move my personal journal here. Have to investigate how to download my content, and whether Medium supports RSS feeds. Yes, I know, most people don’t use RSS feeds any more, except the ones they get automatically by using Wordpress, but Dave Winer had a great idea many years ago, and it’s no less great because Google stopped supporting it.
Ramble, ramble. ‘Nuf said for my first post.