I went through a lot of effort recently to create development system to 'isolate' it from my usual pc activities so that my development system would remain stable.
Then what did I do?
I installed a java update without testing it and now a critical process i need (jdbc to sqlserver 2008) is broken.
And, did I have a backup of java ? NO.
So now I will pay the price of having to figure out how to get this to work again.
What did I learn?
1. Backup your programming environment not just your source code (Possibly in git)
2. Test all updates (I'm running a VM so I can make a snapshot)
I guess the moral of the story is "Experience is what you get when you don't get what you want."
Sunday, November 27, 2011
Saturday, November 19, 2011
I cut my teeth on UNIX 25 years ago and the first text editor I ever leaned to use was vi (on AT&T UNIX) . Over the last 25 years computer interfaces have progressed from ASCII to GUI and programming has progressed from command line to IDE's and I've moved along with with then. But recently I moved my development system from Windows to Linux and had rediscovered VI. Here are my 7 reasons that I still like it and one new one:
- It runs in pretty much any terminal environment
- Being able to open and edit multiple files with a wildcard from the command line
- sed scripts for mass edits
- You can delete a word or a series of words with 2 or 3 keystrokes
- The dot (.) repeat last command key
- Never having to touch a mouse
- Being able to impress younger colleagues
One new reason that vim provides:
- Groovy Syntax highlighting
By the way you can install vim on your windows machine too so you can have these advantages anywhere.