Archive | November, 2009

recommended conventions for RESTful URLs

These are the recommended conventions for RESTful URLs, based on work pioneered by Ruby on Rails, which again is closely modelled over Atompub . Following these conventions for both HTTP method names and URL construction will allow your application to be consumed by ActiveResource, Jester, and other RESTful clients. Note that Rails 1.x used “;edit” and “;new” in place of the simpler “/edit” and “/new” recommended going forward.
(Link: recommended conventions for RESTful URLs)

Go Test It – Automated Cross-Browser Functional Testing (GoTestIt)

Go Test It helps you create better web apps in less time. With our automated test infrastructure you can continuously verify that your web application or website works correctly in many different browsers.
(Link: Go Test It – Automated Cross-Browser Functional Testing (GoTestIt))

Dress – transform XML with Ruby

Honestly, there’s not much to it. A Dress is just a sequence of transformations you perform on a DOM tree. Unlike XSLT though, the transformations are performed directly on the DOM tree. That is to say, they are destructive.
(Link: Dress – transform XML with Ruby)

Learn the five secrets of innovation –

Researchers say they have identified five skills that drive innovation:

Associating: The ability to connect seemingly unrelated questions, problems or ideas from different fields.

Questioning: Innovators constantly ask questions that challenge the common wisdom. They ask “why?”, “why not?” and “what if?”

Observing: Discovery-driven executives scrutinize common phenomena, particularly the behavior of potential customers.

Experimenting: Innovative entrepreneurs actively try out new ideas by creating prototypes and launching pilots.

Networking: innovators go out of their way to meet people with different ideas and perspectives.
(Link: Learn the five secrets of innovation –

Gruber's URL Regular Expression Explained

While America threw on its eating pants and combed the Thursday circulars for deals, John Gruber spent Thanksgiving preparing to unveil his regular expression for finding URLs in arbitrary text.
(Link: Gruber’s URL Regular Expression Explained)

My top 7 RSpec best practices | Dmytro Shteflyuk's Home

I use RSpec in all my projects. It’s really hard to overemphasize how helpful it is and how much easier becomes your life if you have good specs coverage. But its outstanding flexibility enables many ways to make your specs awful: horribly slow, over-bloated, even non-readable sometimes. I do not want to teach you BDD and RSpec here, but instead I will give you some ideas how to improve your specs quality and increase efficiency of your BDD workflow.
(Link: My top 7 RSpec best practices | Dmytro Shteflyuk’s Home)

FreeTrack is a webcam-based optical motion tracking application

FreeTrack is a free optical motion tracking application for Microsoft Windows, released under the GNU General Public License. Its main function is inexpensive head tracking in computer games and simulations but can also be used for general computer accessibility, in particular hands-free computing. Tracking is sensitive enough that only small head movements are required so that the user’s eyes never leave the screen.
(Link: FreeTrack is a webcam-based optical motion tracking application)

Why Google Wave Sucks, And Why You Will Use It Anyway

this post outlines how you’ll probably use Google Wave in the future and also gives you advice on how to implement it in your company or your team of coworkers. It also reveals some big usability problems in the current version. Those issues aside, I would like to show you the advantages of the “wave” once again and describe some cool use cases that might make you love it at some point in the future.
(Link: Why Google Wave Sucks, And Why You Will Use It Anyway)

So you wanna be a user experience designer — Step 2: Guiding Principles

20 Guiding Principles for Experience Design
1. Stay out of people’s way
2. Present few choices
3. Limit distractions
4. Group related objects near each other
5. Create a visual hierarchy that matches the user’s needs
6. Provide strong information scent
7. Provide signposts and cues
8. Provide context
9. Avoid jargon
10. Make things efficient
11. Use appropriate defaults
12. Use constraints appropriately
13. Make actions reversible
14. Reduce latency
15. Provide feedback
16. Use emotion
17. Less is more
18. Be consistent
19. Make a good first impression
20. Be credible and trustworthy
(Link: So you wanna be a user experience designer — Step 2: Guiding Principles)