Just picked up the beta third edition of this awesome book tonight and I was thoroughly enjoying even the beginning chapters. I really love the way these books have been written and my hat is most certainly off to the Sam, Dave, and David (we’re not on a first name basis but if you’re into rails you know who I’m talking about).

After reading the first couple of chapters, I jumped forward to migrations as I was having trouble recently when hacking about with an app that my good friend Malcolm and I have been working on together. After a page of explanation _all_ my questions had been answered.

It’s not only exciting to get this book because it’s such and awesome reference but because I have been wanting to get back to working with rails for a while now. Sorry to gush like a little school girl but you should go buy the pdf now if you are _at_all_ interested in developing with RoR.

happy hacking!

For the SharePoint developer’s group I run in NYC I created a quick STSADM extension that outputs all of site, subsite, list, and list item permissions for a given SharePoint site.

By piping this output into a file you can create a baseline to compare to at a later date with something like winmerge. Thus you have a simply way to verify your site permissions should you need to. The idea was to illustrate how easy it is to create extension for STSADM, but I ended up with a useful utility in the process.

Code here.

Also, if you look at the code you’ll see that there is in fact an interface that all of the “Permissionable” objects implement (ISecurableObject) and as a result the methods for retrieving their Roles and Rights can be generic. Contrary to my earlier post here.

If you have any questions or are interested in attending the next meeting of the New York SharePoint Developer’s Group send me an email at john.bender at hensongroup.com.

Enjoy!

I started this project a long time ago to learn Ruby and never got around to making it really useful. Well I just resurrected it and I think it could be useful for people working with C.

Basically it just does all the dirty work of taking your C methods and making them available for Ruby via a bundle file. The next step is to build out a Ruby unit test script with stubs for each of the methods in the bundle, thus making it very easy to unit test your C code.

Check it out here.