satyan

Agree with your initial point. It's quite easy and intuitive for us non-designers too. Been using it past couple of months and prototyping my apps here.

@cdavid agree with you on forward thinking.

Don't agree on Unit test being trivial. Infact, it is one of the things that aid you with changing specs and code. It helps you change your code with confidence. That really matters.

I appreciate your overall point, had just one correction. thanks.

Seems down.. Can also view a copy here.. http://onsoftwareandstuff.com/2010/10/12/productivity-tips-f...

@RiderOfGiraffes The write-up is about a bottom-up approach in making organizational decisions. Most of the decisions as we know are made right at the top, with minimal understanding of what people on the ground are actually thinking about.

Once you start listening to your people and pick your organizational directions from there, the whole decision making process gets more efficient.

Keep the floor open for different kind of discussions. Keep looking at what discussions are catching heat (more people talking about it). Pick your directions from them. That was the intent.

Eg. Which technology is the most popular among our folks? What kind of clients are liked by our folks? What kind of work do our people prefer? etc. etc.

@brazzy yeah.. that stands out a bit. It just means that technology is chosen without understanding what it is for. There are so many choices available nowadays.. e.g. if one needs faster development/release cycle, you choose Rails, etc..

Thats the context. Thanks.