Often times with RESTful services, a particular URI might need a further level of detail than simply /widget/id — that is, a particular resource might be further segregated by date (i.e. give me the representation of a widget with an id of 29 on the date 04-09-2009). Thus, the URI pattern one would like to support in Grails is more like:

Read more ...

I recently stumbled across Project Euler, which is a hip website containing quite a few different math challenges. The idea being that people can attempt to solve any particular challenge which ever way they can (that is, in any language and with any algorithm) — the site doesn’t provide answers either — you must create an account and submit your answer. Project Euler will then check your answer and issue a response — correct or incorrect.

Read more ...

Agile testing is about two things: a whole life-cycle and whole team approach to testing. The whole life-cycle aspect stresses leveraging testing throughout a hip process as opposed to a distinct period. Likewise, a whole team approach welcomes all parties to the quality table as everyone (yes, that means all stakeholders) accepts responsibility for building in quality.

Read more ...

As I elaborated in two previous hip posts entitled “Agile testing: what it’s not” and “Agile testing: what it is” agile testing boils down to two fundamental aspects — it’s about a whole life-cycle and whole team approach to testing.

Read more ...

Are you building hip RESTful services in Grails that leverage XML? Because it’s your bag, do you want to test these services, easily? If so, then I’ve got a tool for you, baby. Grails’ Functional Testing Plugin makes verifying XML based web services a snap, baby!

Read more ...

In a previous post entitled “Agile testing: what it’s not“, I attempted to define how testing has been traditionally done; with the stage set as the status quo, my definition of agile testing hopefully will make a lot more sense.

Read more ...

When working with Grails (especially, when slapping it over legacy database, man) it’s often helpful to see the hip SQL the framework generates when manipulating domain objects. As mapping a legacy database to Grails can be tricky (but indeed, solvable, baby!), seeing generated SQL can unveil incorrect mapping, etc.

Read more ...

Because it’s my bag, I’ve been asked on more than one occasion the question: “what is agile testing?” — that is, what does Agile mean to traditional QA teams?

Read more ...

Interacting with RESTful web services couldn’t be easier with Groovy’s HTTPBuilder.

Read more ...

I recently had the pleasure of chatting with Alex Miller, who is a respected Java concurrency and scalability enthusiast (and fellow NFJS speaker) who works on Terracotta, an open source, Java-based clustering system. In this JavaWorld sponsored talk, Alex demystifies Terracotta, explaining the programming magic that enables enterprise customers to run 50 to 100 JVMs on a single application server instance.

Read more ...

Occasionally during the course of writing a hip easyb story or specification, you might run into a condition that requires a forced failure. That is, based upon some behavior of the code under verification, you might explicitly want easyb to fail a particular scenario.

Read more ...

Amazon Simple Storage Service (or S3, man) is a publicly available service that hip developers can leverage for storing digital assets such as images, video, music, and documents. S3 provides a RESTful API for interacting with the service programmatically.

Read more ...

Online social networking is all the rage these days, man! In DeveloperWorks’ “Social mashups with Groovy” article, you’ll learn how to build a social network with Google Maps, Twitter, Groovy, and Ajax. By combining a Google Map with location information that Twitter exposes, you can create a mashup that allows people to view Twitter in light of a particular location. The simple application this article builds lets users view a map of their Twitter friends, a.k.a: hip geo-view of their entire network.

Read more ...

In three earlier posts, I discussed the notion of Development 2.0, which aims to leverage open-source technologies and borrowed infrastructures to ultimately produce working software faster.

Read more ...

Because it’s my bag, in two earlier posts, I suggested that the future of software development is already here — that is, Development 2.0, which strives to produce software faster by leveraging open-source technologies and borrowing other people’s infrastructures, addresses the frustrati

Read more ...