Jeremy D. Miller -- The Shade Tree Developer

Sponsors

The Lounge

Syndication

News

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
The first step to coding faster

Forget all the Ivory Tower stuff I like to prattle on about, if you want to be a more productive programmer, learn to keep your hands on the keyboard instead of reaching for that mouse.  It'll make the mechanics faster and leave more time for the "thinking work."


Posted Tue, Oct 24 2006 10:26 AM by Jeremy D. Miller

[Advertisement]

Comments

Steve Donie wrote re: The first step to coding faster
on Tue, Oct 24 2006 11:09 AM

Back when I used to do accessibility work, we would encourage developers to take a day and drop their mouse down behind their desk so that they could get a sense of what it was like for a blind person - someone who MUST use only the keyboard. I did this for a long time and have learned tons of keyboard shortcuts. When you're pairing, always share them with each other and you'll learn tons quickly.

Budlight wrote re: The first step to coding faster
on Tue, Oct 24 2006 11:36 AM

I'm a big believer in using the keyboard, I'm also a big believer in the IBM keyboards with their stick button mouse(not sure of it's proper name) instead of just the trackpad.  I find I'm way more productive using my laptop with some things, than I am with my desktop for this reason.  I wish more laptop manufacturers included this, it seems to be getting phased out.

Robb wrote re: The first step to coding faster
on Tue, Oct 24 2006 11:40 AM

You can have my mouse. I use a Fingerworks Touchstream (stupid @!$%@ are out of business though), so my keyboard IS my mouse.

However, I totally agree that you shouldn't ever force anyone to switch devices to get a job done. Hard thing to acheive (and not always possible), but it is a good habit to get into.

Chris wrote re: The first step to coding faster
on Tue, Oct 24 2006 11:53 AM

I definitely agree. I used to do my coding in vim, read mail in mutt, and use Ratpoison as my window  manager - it's hard to get used to, but it's impressive to see the speed at which things can get done without reaching for the rodent.

John wrote re: The first step to coding faster
on Tue, Oct 24 2006 1:17 PM

A few months ago I did a search for some keyboard shortcuts to make my programming fast but didn't find a site that helped. Any suggestions? Can you share some shortcuts?

Jeremy D. Miller wrote re: The first step to coding faster
on Tue, Oct 24 2006 3:11 PM
camera wrote re: The first step to coding faster
on Tue, Oct 24 2006 5:00 PM

I created a VisualStudio shortcuts cheat sheet a while back.  

http://iamacamera.org/default.aspx?section=home&id=43

Jeffrey Palermo wrote re: The first step to coding faster
on Tue, Oct 24 2006 6:25 PM

Steve,

You certainly did teach me a TON of keyboard shortcuts, and I thank you.

With VS.Net bare, it's pretty hard to achieve this, but since I use Resharper as my IDE inside VS, I reach for my mouse very seldomly.

ulab wrote re: The first step to coding faster
on Wed, Oct 25 2006 11:13 PM

Try rewiring all your editors to the same keyboard shortcut. For example, I use Source Insight, VS .net and Editplus. Ctrl + Shift + F searches in files in all three. Ctrl + shift + f11 is for list of windows open.

For custom rewiring, remember that in VS when you go to Tools-->Option -->Keyboard, you can type the keyword (like split) to show the commands related to that. That way you can narrow/find what you want  to wire to keyboard. (The other day I found that there is a macro to beginning of a function (even if it outside) the screen by typing ' ').

Backup your settings in VS about once a month. I cannot live without my settings.

The worst one is sqlwb. The only automation you can do is with those free keys (Ctrl + 1, etc. ). If you select a text and press, say ctrl +3 and Ctrl + 3 is wired to a sproc, the selected text will be passed in as argument to the sproc.

So I have sprocs  (in master)

create proc sp_listall

(

 @tablename varchar(50)

)

as

string sql varchar(300);

set sql = 'select * from ' + @tablename

exec (sql)

which lists all the rows in the table. (another sproc for listing all the columns in table)

Helpful when doing dev work.

hth

ulab wrote re: The first step to coding faster
on Wed, Oct 25 2006 11:18 PM

beginning of a function (even if it outside) the screen by typing ' ').

Left out ....

by typing 'begin' in show commands containing....

jak321 wrote re: The first step to coding faster
on Tue, Mar 27 2007 3:13 PM

Don't forget to start at the very beginning: learn to touch type.  No looking at the keyboard AT ALL.  Although most programmers "multi-finger" hunt-and-peck at a fair rate, most can't actually type, and its just stupid.  

soulposition wrote Put the mouse down..
on Wed, Mar 28 2007 11:24 AM

Coding Horror: One of the quickest ways to increase your productivity on the computer is...

Nick Parker wrote Choosing a Text Editor
on Tue, Apr 10 2007 8:08 PM

Choosing a Text Editor

The New Interface Advocate » Blog Archive » The misused mouse, part 1: The story of the mouse's decline wrote The New Interface Advocate » Blog Archive » The misused mouse, part 1: The story of the mouse's decline
on Sat, Jun 30 2007 9:42 PM

Pingback from  The New Interface Advocate  » Blog Archive   » The misused mouse, part 1: The story of the mouse's decline

Working Faster !!! « Journeytogeek’s Weblog wrote Working Faster !!! « Journeytogeek’s Weblog
on Tue, Feb 17 2009 4:57 AM

Pingback from  Working Faster !!! « Journeytogeek’s Weblog

Nick Parker wrote Choosing a Text Editor
on Sun, Mar 22 2009 1:02 PM

Choosing a Text Editor

the birdie wrote re: The first step to coding faster
on Fri, Oct 2 2009 9:03 AM

I totally agree!  When I was a kid, all we had was DOS.  My mom taught me some commands and the basics of QBASIC.  Spent many hours trying to hack the computer lol.  Those were the good days :)

Add a Comment

(required)  
(optional)
(required)  
Remember Me?