peace on the web, too

• Data Structures and Algorithms with Object-Oriented Design Patterns in Ruby
  Data Structures and Algorithms with Object-Oriented Design Patterns in Ruby
  (tags: ruby programming algorithms book patterns design ebook free)

Do you feel down today? Broken? Unhappy with your life website? Just check you spam comments :D

Look what comments I had on one of my blogs spam filter today:

• Nice design!
• Cool}Cool!
• Pretty nice site!
• Brilliant site!
• Super site!
• Thanks for your work!
• Added to bookmark, thanks!
• Good site!
• (man! isn’t it obvious my site is brilliant, not just good? this one pisse dme off)
• Great site!
• It’s very good site, thanks!
• (it’s very good for me too, thanks!)
• Unreal design, cool!
• (now you’re talking!  yeah! I rule!)
• Thanks for helping!
• (you’re welcome)
• Fantastic design!
• Best wishes to WM of this site!
• (happy easter to you too)
• Cool design, great info!
• [repeat this a couple (100) of times]

In an exclusive nine-part dialogue with an imaginary eBay
Architect, we present an accessible discussion of the
REST vs. SOA issue.

Although eBay have what they call a ‘REST’ interface, it is, in
fact, a
STREST
interface, and only works for one of the many function calls
that they make available via SOAP (GetSearchResults).

In this dialogue series,
I argue the case for eBay to adopt a truly REST approach to
their integration API.

Scott Bellware has a great post about what makes an unit test and what an integration test.

…it isn’t a unit test if:

• It talks to the database
• It communicates across the network
• It touches the file system
• It can’t run at the same time as any of your other unit tests
• You have to do special things to your environment (such as editing config files) to run it.

Seems like a good idea to separate units and integration tests using these criteria and optimize then based on speed and isolation possibilities.