Resolutions. Bah. I've never done New Year's resolutions. So to change
it up a bit, this year my resolution will be to have at least one
resolution. I'm not sure what it'll (or they) will be yet. I'll have to
think about it. I'll write it here on my blog, but 1) I know nobody
reading this will care about my resolutions and 2) chances are within a
month, neither will I. But I guess it's worth a shot. I hear all the
cool kids are doing it.
Update:
My New Year's Resolutions:
1) Blog more.
Alright after a loooooong hiatus, I'm back. I still struggle with figuring out what to write, but I'll do my best. Since my last post, a LOT has changed - and is part of the reason I've been away. I started a new job in Cambridge, MA at a company called Six Red Marbles and we've been working practically non-stop on our current project. We finally have a few days of down time in between release candidates to take a break. I'm looking forward to being able to talk about it more once it's launched.
So I haven't been very good about keeping up on this blog. I guess it's because I haven't been in the habit of writing the past several years. Back in the day, though, I was quite good at it. It's also due to the fact that I've been struggling to find the "perfect topic" to write about each time. I've felt the need to maintain a certain level of professionalism, as this website also (as it currently stands) serves as a gateway to my Infonate Web Services company. At some point, when the time/financial resources are available, I'll completely separate that out.
If you've been to nateprouty.com prior to today (05/22/2008), you'll notice there have been some significant changes. The website now has a wide layout, allowing for left and right side content. There is also a brand new support system in place. Those needing to contact me for development work - either for an existing project or something new - should fill out that form as needed. This is the best way to ensure I have all the pertinent data pertaining to your needs.
Recently I found myself in a catch-22 with a Drupal site I have running locally as a sandbox for development. A module I had enabled (SecurePages) was working great. Later, though, when I went to start up the web server after I had taken it down, I couldn't establish a connection to the SSL that the module requires. The server wouldn't start because of this. I first tried turning off the the "Secure (SSL/TLS) Connections" includes call in httpd.conf.
