Anthony Panozzo's Blog

Today's post is a short one that I have incorporated into Writing With Vim and will publish when I add a few more changes.

When Vim's spell check is enabled, words that are not known to be good are highlighted as incorrect. This is the behavior that we want generally. However, there are certain types of text that are commonly marked as incorrect, and it can be tedious or impossible to constantly add them to your dictionary.

One example would be URLs. These are marked as incorrect by Vim by default, but it would be nice to just tell Vim to ignore them from the spell check so you can navigate spelling errors more quickly and to reduce the amount of noise on the screen. You can accomplish this with:

I did my first programming in Applesoft BASIC on the Apple IIc, and then I did quite a bit in middle school and early high school in QBasic on a 486 machine.

I've been in a bit of an archival kick lately. I recently started a small project of getting some data off of my Apple IIc disks, which is going well. I thought: maybe there is a way to get my old QBasic programs running as well.

QBasic ran under MS-DOS, the command-line interface of pre-Windows and early Windows computers. You can see a more modern version by typing cmd at the Windows program. I wanted to get a way that I could look at my old programs and to preserve and distribute them to others.

I looked around for a QBasic emulator, and except for the well-known and battle-tested DOSBox DOS emulator, could only find a partially-completed QBasic interpreter written in JavaScript. It didn't have graphics mode, and many of the programs that I wrote used this.

Archive.org has a huge collection of DOS games. This is great for preserving old software. You can even play old games, although any game saves won't persist between page reloads¹. The DOS collection runs on em-dosbox, which compiles the DOSBox DOS emulator from C++ to Javascript using emscripten. Fortunately, all of this is open source.

In a Slack organization that I am a part of, someone asked:

Has anyone ever heard of anything that takes Github repos and assigns them some sort of "reliability score"? Something that takes stars, commit frequency, PRs, open/closed issue ratio, issue closing time, etc. into account and gives them a score? It would be really nice for choosing between two or three repos that do similar things.

I had some thoughts on this since it is something that I have done in the past, and took them and extended for this post.

Existing alternatives

The Ruby Toolbox tries to give a rough score for ruby gems based on the features above, and it gets most of the way there. It provides a good overview for classes of gems to get a sense of how well maintained they are. Usually when I am trying to find a gem that does something, I start here. Over time you get a sense of a language's ecosystem and this is less valuable, but it is still useful for finding new gems that might do that thing better.

Karabiner (formerly KeyRemap4MacBook) is a tool that lets you remap certain keys on your keyboard. I find this useful as a developer and someone who writes words in a few ways.

Mega Fast Key Repeats

When I pair with someone for the first time or give a presentation, they usually ask "how are you moving the cursor so fast?" I use Karabiner to crank up the cursor speed. This is most useful for navigating quickly between letters, words, and sentences. Also, it's useful for quickly killing characters. At first the cursor seems to be flying around, but soon you gain control and can't imagine working another way.

My current settings (see the "Key Repeat" tab) are for a "delay until repeat" of 250 milliseconds and a "key repeat" of 10 milliseconds. Any shorter of delay until repeat causes me to add extra chaarractersss when I don't intend to do so. Similarly, 10 milliseconds of key repeat allows me to be pretty precise in cursor placement without sacrificing nearly top speed.

There is a famous 1932 World Series game that legendary baseball player Babe Ruth played in. In the game, he may or may not have pointed to the bleachers before hitting a critical home run, which intrigues fans to this day. There's something compelling about the idea of calling your shot, or saying what you are going to do and then doing it.

Calling your shots

My productivity advice is to call your shots every day you sit down to work.

At the beginning of each day, publicly state what you're going to accomplish, and then update the list throughout the day. Make a list of the three or so most important things you are going to accomplish. If they aren't important, why are you doing them? Ideally, you can tie these back to company or team objectives.

Here's an example of what I might set out to do during a day. I usually post this to Slack in an appropriate channel, but you can use the best communication method for your team:

2016-02-02</br></br> [√] Fix forward-progress onboarding issue when there is a 500</br> [√] Sign up for Salesforce backups { OKR: Salesforce }</br> [√] Work with KP to test out a Salesforce email sending to Mandrill test environment</br></br> Blockers: need help figuring out why the PDFs are not generating and updated TOS/ROI at on some Salesforce accounts.</br></br> Headed to the Indy Vim meetup tonight, where I'll be presenting on "using text objects and surround.vim effectively".

I try to update the task list throughout the day for: