{ on programming and the internets }


by Louis Brandy

My New Year’s Resolution

I am a bit of a procrastinator.

Yes, yes, that doesn’t exactly make me special, but I’m talking specifics here. I’m a programmer, and a procrastinator. And that can mean troubles.

For the next year (and/or the first three weeks of January, whichever comes first), I’m going to automate/refactor/abstract any operation I do for the third time. I’ve noticed far too many insignificant hiccups in my workflow that go ignored. It’s just that the marginal cost of putting up with the annoyance is so much less painful than sitting down and writing the script (or a special commands, or option, or what have you). Maybe I’ll do it next week. And next week becomes next month. And now I’ve started to realize niggling annoyances that have gone on for years. Yes, years.

Let me give you two examples…

Oprofile

I use oprofile constantly.

sudo opcontrol --reset
sudo opcontrol --start
./run_my_code
sudo opcontrol --shutdown
opreport -lt1

I’ve typed that out, in full, for probably close to 3 years now. Why? Other people have noticed. I’ve noticed. I’m pretty sure no less than two of my co-workers would have edited my aliases for me, if I had let them. Well, I finally sat down and wrote the 10 line python script that will do this (and a handful of other useful oprofile functions) for me. It took about 10 minutes. Sigh.

Emacs vs vi

I’ve always been an emacs fan. I probably always be. However, there is one part of vi that has always made me jealous. The name. vi is just such an amazingly easy name to type instead of the incredibly laborious emacs. As a young kid, I decided to fix this and I added an alias for my customized emacs launch as “em“. Yes, I aliased emacs to em. I’ve been using it for years. And it’s extremely stupid. Extremely, extremely stupid. It doesn’t take much thought to figure out why “em important_file.cpp” can become a disaster. (extra stupid note: compare the locations of the typo keys).

I know it’s stupid, and yet it continues. Every time I move my environment over to a new machine, I copy the alias over. Why? Because it’s always been there, and it’s on all my machines. Because I can’t fix it right now. I’ll fix it next time. Gah. It ends now. I will never type em again.

trackback

5 Responses to “My New Year’s Resolution”

  1. January 4th, 2010 at 7:00 pm

    Ben Combee says:

    I’ve always setup ‘e’ as an alias for “emacs -nw”. If I’m going to use it a lot, I want one letter :)

  2. January 11th, 2010 at 3:14 pm

    Brad says:

    Pretty sure being a programmer automatically makes you a procrastinator… Just the way it is…

  3. January 13th, 2010 at 1:46 pm

    Jay Tennier says:

    I’m not sure why you don’t just alias emacs to ‘vi’.

  4. January 14th, 2010 at 4:57 am

    Jed says:

    @Ben

    You’ll love changing that to “emacsclient -t”

  5. April 6th, 2010 at 8:21 pm

    Brendan Miller says:

    I use:

    alias e=’emacsclient -n’
    alias ee=’emacsclient -n -c’

    so I set up my environment, do:
    emacs –daemon

    Then open a window with:
    ee

    Then add new files the the existing emacs instance with:
    e myfile

    Or just load files from dired…

Leave a Reply


Need a new job?