We all just spent a few dedicated days listening to talks and having long hard discussions about building web apps in Miami at

We all just spent a few dedicated days listening to talks and having long hard discussions about building web apps in Miami at
Ok everyone, we here at the wojo group are getting pretty excited for next week. On Saturday, we’re packing up our cars and driving straight through the night. We’re not stopping until we hit Miami. Why, you may ask? FOWA 2009!
I had a recent discussion about web app security and we were talking about the not-so-distant past when SQL-injection was the scariest thing since polio. 90% of these attacks didn’t try to return everyone’s credit card information from a database (people knew pretty early to be careful when storing this stuff), they were attempts to simply return a username and password. I wanted to go over a simple method for guarding against password retrieval that should be second nature for any developer.
Over the past few years, our company has had several clients who have needed a smaller shopping cart, usually to only sell a couple items. Because we expected sporadic traffic, we were tentative to go with a packaged shopping cart and merchant service. That just seemed like a lot of overhead. Thus, I have developed a few different ajax carts using paypal. I realized it would be nice to package this up, and create a lightweight, easy-to-use, flexible shopping cart.
So we made simpleCart(js). The cart is a 10.5kb javascript file that uses cookies to keep track of the items in the cart. Thus, simpleCart(js) doesn’t require any databases or programming. You simply need to know some basic HTML and have the ability to copy and paste. However, it can easily be expanded to use databases or contain more advanced options.
Here’s 10 really easy steps to getting your sites optimized for speed.
Recently I have been discussing with some fellow coders the benefits of plugins, and when you should write your own code. I basically wanted to throw out a couple of ideas and hope for some discussion on the topic. Let me know what you guys think and I’ll do a follow up soon.
I recently had a need for a login system that needed a ‘remember me’ function. After hours of looking through countless blogs, I came to the conclusion that either (1) people don’t use a remember me function with Rails logins, or (2) they don’t write about it. In this article, I outline a simple remember me system using the cookie variable in Rails that will tack on to most custom authentication systems.
Well organized beautiful code can not only reduce future and current development time, but it can also have many pleasant adverse side effects.
We recently beta launched a new site, motionspire.com. Our main goal for the launch was to get statistics from user testing, mainly from a targeted audience. In order to keep a limited user base, we wanted to make visitors create a beta account, and use a login system in order to view the site.
I wanted to create a quick and simple login system that was, most importantly, temporary. The authentication didn’t require a lot of security because no user information was stored in our db other than an email and password. I also wanted to contain all the code for the system (as much as possible at least) in a few different directories, so I can easily remove the system for the main launch.