Comments on: an open letter to ipayroll redux http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux Ruby on Rails developers from Wellington, New Zealand Tue, 02 Feb 2010 09:42:18 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Cary http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux/comment-page-1#comment-88 Cary Sun, 11 May 2008 21:16:52 +0000 http://codetocustomer.com/?p=39#comment-88 While we could require prospects to give out their email address to sign up for a free trial we try to make <a href='http://www.useit.com/alertbox/990307.html' rel="nofollow">sensitive use of email</a>. And as for the ol' login/password box on a HTTPS page we try not to use <a>Non-Standard GUI Controls</a> - although your comments about our Unauthorized page are noted. However, the more compelling and interesting reasons for using "Org ID's" and HTTP Authentication are actually <a href='http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_2_1_1' rel="nofollow">much more fundamental</a>. Having a proper URI Space for everything plays much nicer on the World Wide Web - for example we can bookmark and email links to anything in iPayroll, and everything plays very nicely with the rest of the the web's infrastructure (e.g. caching). While we could require prospects to give out their email address to sign up for a free trial we try to make sensitive use of email. And as for the ol’ login/password box on a HTTPS page we try not to use Non-Standard GUI Controls – although your comments about our Unauthorized page are noted.

However, the more compelling and interesting reasons for using “Org ID’s” and HTTP Authentication are actually much more fundamental. Having a proper URI Space for everything plays much nicer on the World Wide Web – for example we can bookmark and email links to anything in iPayroll, and everything plays very nicely with the rest of the the web’s infrastructure (e.g. caching).

]]> By: Bill http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux/comment-page-1#comment-87 Bill Fri, 09 May 2008 10:20:11 +0000 http://codetocustomer.com/?p=39#comment-87 Well done Cary for responding in a public forum. I use your iPayroll service for the Daycare Centre I help manage. I have to say the service is great, and the amount of information you have at hand is amazing. Nik's suggestions (if applied) would make your service even better. Well done Cary for responding in a public forum. I use your iPayroll service for the Daycare Centre I help manage. I have to say the service is great, and the amount of information you have at hand is amazing.
Nik’s suggestions (if applied) would make your service even better.

]]> By: Nik http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux/comment-page-1#comment-85 Nik Thu, 08 May 2008 02:51:42 +0000 http://codetocustomer.com/?p=39#comment-85 @cary: The disclaimer is necessary because some other people have taken offhand comments the wrong way. Want to make sure my big mouth doesn't get me into too much trouble :) Awesome to see fixes coming in immediately as things come to your attention - that's startup-speed, I remember doing the same thing answering support at PlanHQ. You guys should be proud of that! @cary: The disclaimer is necessary because some other people have taken offhand comments the wrong way. Want to make sure my big mouth doesn’t get me into too much trouble :)

Awesome to see fixes coming in immediately as things come to your attention – that’s startup-speed, I remember doing the same thing answering support at PlanHQ. You guys should be proud of that!

]]> By: Cary http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux/comment-page-1#comment-84 Cary Thu, 08 May 2008 02:18:58 +0000 http://codetocustomer.com/?p=39#comment-84 Re: Your disclaimer - no need for that, we like constructive criticism and I appreciate that you like our service enough to take the time. I'll comment further on your other points in due course. Re: Your disclaimer – no need for that, we like constructive criticism and I appreciate that you like our service enough to take the time.

I’ll comment further on your other points in due course.

]]> By: Cary http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux/comment-page-1#comment-83 Cary Thu, 08 May 2008 02:15:50 +0000 http://codetocustomer.com/?p=39#comment-83 #5 - alignment. That report wasn't up to our usual standards (it fairly obscure, but that's no excuse). It's now been tidied up a bit. http://www.ipayroll.co.nz/org/sample/tax/ked (BTW we like zebra striping - and when I saw that article recently I didn't see anything to make me change my mind). #5 – alignment. That report wasn’t up to our usual standards (it fairly obscure, but that’s no excuse). It’s now been tidied up a bit.
http://www.ipayroll.co.nz/org/sample/tax/ked

(BTW we like zebra striping – and when I saw that article recently I didn’t see anything to make me change my mind).

]]> By: Cary http://codetocustomer.com/blog/2008/05/an-open-letter-to-ipayrol-redux/comment-page-1#comment-82 Cary Thu, 08 May 2008 02:10:24 +0000 http://codetocustomer.com/?p=39#comment-82 Nik, #3 (tabs) - good call, that was just plain wrong. It's now better. http://www.ipayroll.co.nz/org/sample/payroll/pay_reports Nik, #3 (tabs) – good call, that was just plain wrong. It’s now better.
http://www.ipayroll.co.nz/org/sample/payroll/pay_reports

]]>