Today I installed Grails on my work laptop.

And then set to try the quick-start example.

I soon ran into a problem when I tried to create my application using the command

grails create-app MyApp

I got the following error

The syntax of the command is incorrect

I spent some time trying to debug the grails.bat file – but soon fell back on time-tested strategy. If someone has solved it- Google will know about it !!!

And it turns out -I had not installed Groovy !!!

Hmmm – I would have thought either Grails should have had groovy bundled with it or at least politely warned me that I do not have Groovy installed.

And whatever happened to the good old message NoClasssDefFoundError ???

Anyways- once I got Groovy - things went pretty smoothly

And I had my simple app- up and ready in no time.

I also did the following…
Setup up my GROOVY_HOME and GRAILS_HOME
Setup the path to include %GROOVY_HOME%\bin and %GRAILS_HOME%\bin

I know – I would have discovered this beforehand- had I taken the time to read the readme.txt – but I think Grails team could have done a better job by prompting with a better message

 

I think today is the second or maybe third day when Hibernate’s documentation has been inaccessible.

Thank god for Google cache !!!

Well I hope it gets back soon.

UPDATE: Seems like its back!!!

 

I am finally done , reading this book ”Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin.

It was an excellent read.
I think it has changed the way I will look at software development in future…

It’s a collection of very practical advice- difficult to argue. Most of the stuff is what you have realized at some point or other while programming. reading it in the print- gives words to those thoughts

The projects in this book – I skipped. I am sure they are good and effective way of putting this in practice- but I would rather read the code that I have written and look for smells there.

There were only two things that I didn’t agree with
One: On TDD. I cant reconcile to the way of programming the way as prescribed by TDD. Its way too much for me
Second: Importing java classes by using * rather than importing classes by specific names
I like to use specific class names- it keeps the dependencies well defined rather than keep them generic. It also makes it easier to search for dependencies by using plain search rather than using IDE.

And with all these fancy editors- its so easy to collapse the imports and remove the ones which are not needed

And if need be – you can clearly see what is is the dependency network (without running a heart-stopping dependency search on your IDE)

Finally- I am not sure why the book has Agile in the title

All advice was practical and mostly from the trenches- right at the code level.

I see no reason why the suggestions in this book cant be adopted by someone using Waterfall methodology or any other process.

I did skip some chapters though- 14,15,16. These were detailed case studies and I didn’t feel the need to read them. Reading lines of code in books doesn’t cut it for me

Who would I recommend this book to ?
Any one who is a coder.
Though I am not sure if someone who is still in school would be able to appreciate this as much
You need to have seen the blood on the streets to be able to appreciate the walk around the park.

For review of all chapters- please see this post.

© 2011 Technology Cafe Suffusion theme by Sayontan Sinha