I have posted my paper (An Introduction to Git Version Control...) at my sas-resources.com site:
http://www.sas-resources.com/recipes/an-introduction-to-git-version-control-for-sas-programmers
Thanks to everyone at WUSS who attended, everyone who asked questions and everyone who has given feedback! -s
Tuesday, September 11, 2012
WUSS 2012 Long Beach Paper
Wednesday, August 01, 2012
I Git Busy
While I was on vacation, I got a friendly email reminding me that my WUSS 2012 paper was due July 30th. Yikes! I had exactly one week to get home and write it. My mother calls it procrastinating. I prefer to think of it as Lazy Loading.
So I was a bit busy last week.
But I finished it. And I think it's good. At least, I hope it's good.
It is an Introduction to Git Version Control for SAS Programmers.
You see, back in March I wrote this blog post asking about the version control you use while developing SAS programs:
http://datasteps.blogspot.com/2012/03/version-control.html
Based on the _underwhelming_ response, I assumed most SAS programmers were like me and didn't use a version control system because version control is an enterprise thing and I was doing programming on my own or in small teams. That was until I discovered Git. Now version control is mine. It belongs to me and is part of my workflow. I'm enthusiastic about how it's helped me as a coder. Hopefully my presentation and paper will share that enthusiasm with you.
Tuesday, June 12, 2012
Rainbow Table Salt
DISCLAIMER: I am not an expert at cryptology. But I generally understand the industry best practices and have implemented this stuff on several sites. That said, read on at your own risk :)
There's been a lot of talk about LinkedIN passwords getting stolen. It's an interesting read and it made me think it would make for a good blog post.
If you read the link above you will see them referring to hashed passwords. First of all, nobody should be storing passwords in a data base as clear text. Never, ever, nope. You want to store the password after it's been hashed with a one-way hashing algorithm. One-way just means it's computationally impractical on todays computers to go the reverse direction from hashed string back to password.
<rant>