Comments for The Nomadic Developer

Comment on The Book by Cannon

Cannon — Thu, 19 Jan 2012 20:33:18 +0000

I’m impressed by your writing. Are you a professional or just very knowegldaeble?

Comment on Why I Work At ThoughtWorks (and why you should too…) by Sameer Soman (@SameerSoman)

Sameer Soman (@SameerSoman) — Fri, 06 Jan 2012 10:44:07 +0000

Very well written … and I am myself completing 2 years in TW; and all the reasons resonate so well with me. I can safely say that this is my most enriching professional experience (in overall 20+ years career). Roy indeed has built a good company on great values.

Comment on Why I Work At ThoughtWorks (and why you should too…) by Reflections on 2 Years at ThoughtWorks : Scott Muc

Reflections on 2 Years at ThoughtWorks : Scott Muc — Thu, 05 Jan 2012 00:30:44 +0000

[...] at ThoughtWorks for 2 years now! My colleague Aaron Erickson has written an excellent writeup on why (work at) ThoughtWorks. I couldn't agree [...]

Comment on Why I Work At ThoughtWorks (and why you should too…) by B. K. Oxley (binkley)

B. K. Oxley (binkley) — Wed, 04 Jan 2012 00:37:46 +0000

ThoughtWorks was my favorite of all the employers I have had. I only left after too much full-time travel and not enough time with growing children. Unfortunately, there were not long-term engagement near where I live.

But I would recommend TW over and over to anyone interested. It will be the best job you ever have for all the reasons Aaron gives and for reasons all your own.

Go for it!

Comment on Why I Work At ThoughtWorks (and why you should too…) by rupeshdubey

rupeshdubey — Tue, 03 Jan 2012 23:55:31 +0000

U nailed it .The most imp lesson which I have learned in TW is to be courageous and stand by our principles

Comment on The Book by Mike Battles

Mike Battles — Mon, 31 Oct 2011 03:57:59 +0000

I love the book. I really like that figure 10-1 and think its an awesome way to visualize the week…. only problem is you left 10 hours on the table :) 40+20+42+56=158

Comment on Hourly Rates Considered Harmful by Brian C

Brian C — Thu, 20 Oct 2011 12:34:46 +0000

This applies to any type of deliverable, software, engineering, web development, copy writing, etc.

Although I have an hourly rate in mind, I estimate jobs in half or whole day chunks, and propose an explicit deliverable for a fixed dollar amount. This works best for small projects, say 5 days’ expended effort, and I find it best to break bigger projects into chunks that I can estimate with more confidence.

Comment on Hourly Rates Considered Harmful by Ben Edwards

Ben Edwards — Wed, 19 Oct 2011 03:07:00 +0000

This is a great post. I always say that it is hard to just put your hourly rate out there on its own because, in a vacuum, it will look high. It isn;t until 2 months into a project and we’re nearly done with something other teams told them would take 6 months or more does that rate look a lot better.

Comment on Why Does Custom Software Cost So Much? by benstieglitz

benstieglitz — Fri, 02 Sep 2011 22:00:42 +0000

Regarding “Strong Process” – This quote says it best “Everyone has a plan, until they are punched in the face” – Matt Hugh MMA World Champion Cage Fighter. Metaphorically speaking it’s true. The best plans fall apart, and it’s what you do reaction wise that will keep you moving forward successfully. It comes with knowledge, experience, and most importantly, time.

Comment on Why Does Custom Software Cost So Much? by benstieglitz

benstieglitz — Fri, 02 Sep 2011 21:18:48 +0000

“It is a race to the bottom” – like people selling go karts on ebay, same model, same manufacture, each trying to be cheaper than the next. People use short term profit as the most important metric, which just as ironicly as ’causes even more project failure.’ , it is more expensive in the long run. Cheaper is not better, so when are people going to understand this? Great read / info, as always.