I recently decided that I wanted to learn to program in Cocoa. There wasn’t really a good reason for me to learn it, aside from my desire to learn a new programming language. Also it would be nice to know how to make Mac and iOS apps.
I looked around the net for a good beginner’s guide to learning Cocoa. I found one that I highly recommend. But, before I talk about the book I used to learn Cocoa I should give a quick note about my programming experience.
Prior to entering the PhD program here at CU Boulder, I have no experience programming at all. As my research progressed, I have become rather proficient at programming in Fortran. In addition to Fortran, I have taught myself scripting languages such as Python, Bash, C-shell, perl, etc.
So basically, before learning Cocoa I had no real experience programming in an Objective-based language.
Continue reading Beginner’s Guide to Learning Cocoa Programming
If you are like me, you probably do a lot of your coding on a remote computer. I have known some people who will download all files from a remote computer onto their local system, make changes in a text editor, and then upload the files back to the remote server. This is a very inefficient way of coding, and is just one of the reasons why i choose to write all of my code in VIM.
If you have ready my other posts (specifically Useful .cshrc commands), you know that I like to have the title of the terminal set to my current working directory. However, after exiting VIM, I always end up with the frustrating “Thanks for flying VIM” message in the title.
I had read on other blogs and forums that adding
set notitle to your .vimrc file will prevent the “Thanks for flying VIM” message from showing up.
Well, that didn’t work for me. After a lot of scouring the internet, I was able to find the solution.
Adding this to your .vimrc file will, upon exit from vim, set the terminal title to the current working directory.
Lets face it, nodes randomly go down without warning sometimes. If you’re like me, you aren’t going to consistently check the node status throughout the day. There have been cases where a node has gone down, and I didn’t know about it for a week.
This is very problematic, especially when you run a system that has a small number of nodes that are always in use.
In an effort to resolve both the problem of me not knowing there is a dead node without requiring me to check the node status multiple times a day, I developed a python script to check if there is a dead node. The script is set to run every day at midnight, and if there is a dead node it will send me an email.
Download the script here.
The only edits you should have to make in order to get the script to run on your system are lines 21 – 35.
- Line 21: Change to match your username
- Line 22: Change to match your email address.
- Lines 25-35: Change to whatever email message you want sent.
Now all you have to do is add the script to cron.
And you’re done!