Comments on: Code quality and the fat developer http://www.taylor.se/blog/2009/02/25/code-quality-and-the-fat-developer/ Smart consulting Tue, 08 Jun 2010 05:02:39 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Lu Xun http://www.taylor.se/blog/2009/02/25/code-quality-and-the-fat-developer/comment-page-1/#comment-19197 Lu Xun Wed, 21 Oct 2009 03:12:28 +0000 http://www.taylor.se/blog/?p=205#comment-19197 You got me! I thinks this post is a wake up call for all those developers who doesn't even care about the way they code. The way they work is the biggest hindrance to achieve the success of a project. It also affects the other team player's productivity and efficiency. Wake Up dude! burn some fats! You got me!

I thinks this post is a wake up call for all those developers who doesn’t even care about the way they code.

The way they work is the biggest hindrance to achieve the success of a project.

It also affects the other team player’s productivity and efficiency.

Wake Up dude! burn some fats!

]]> By: Fredrik M http://www.taylor.se/blog/2009/02/25/code-quality-and-the-fat-developer/comment-page-1/#comment-18098 Fredrik M Mon, 23 Mar 2009 07:11:43 +0000 http://www.taylor.se/blog/?p=205#comment-18098 I agree.. We talk often about, time is money, but that is in the short term not in the long term. For the moment I am somewhere between the lazy fizzy bubbliz driking coder, and sometimes I train very hard. I agree..

We talk often about, time is money, but that is in the short term not in the long term.

For the moment I am somewhere between the lazy fizzy bubbliz driking coder, and sometimes I train very hard.

]]> By: Iflexion web developer http://www.taylor.se/blog/2009/02/25/code-quality-and-the-fat-developer/comment-page-1/#comment-18044 Iflexion web developer Fri, 13 Mar 2009 15:56:29 +0000 http://www.taylor.se/blog/?p=205#comment-18044 You are right there. :) And I'm starting to recognize myself, with Tobias too. :) What to do it this case? I think that nowadays you are no one if you aren't working on yourself and don't try to overcome your lazyness and other faults. Just try to form your team of persistant, hard working developers. And stimulate them for who they are, what qualities they have and their progress on themselves. You are right there. :)
And I’m starting to recognize myself, with Tobias too. :)
What to do it this case?
I think that nowadays you are no one if you aren’t working on yourself and don’t try to overcome your lazyness and other faults.
Just try to form your team of persistant, hard working developers. And stimulate them for who they are, what qualities they have and their progress on themselves.

]]> By: Tobias Fjälling http://www.taylor.se/blog/2009/02/25/code-quality-and-the-fat-developer/comment-page-1/#comment-17982 Tobias Fjälling Thu, 26 Feb 2009 08:18:56 +0000 http://www.taylor.se/blog/?p=205#comment-17982 Nice thoughts and I do recognise myself in a lot of what you write. I think it becomes easier if this this focus becomes a team commitment and not only an individual responsibility. A company should should invest time for dedicated meetings in order to discuss such things. This way you feel both the responsibility and the support from team members to actually do good. At the Admeta company, I've started a Clean Code study circle with the purpose of exactly this having one hour each week that we meet. One hour every other week for Clean Code book discussions (details in my blog) and one hour every other week for other types of discussions/presentations. I think we see the fruits of this already at our company with a different mindset and more enthusiastic athmosphere. No man is an island. PS. How do you measure code quality? Are there any good advices to get here? Nice thoughts and I do recognise myself in a lot of what you write.

I think it becomes easier if this this focus becomes a team commitment and not only an individual responsibility. A company should should invest time for dedicated meetings in order to discuss such things. This way you feel both the responsibility and the support from team members to actually do good.

At the Admeta company, I’ve started a Clean Code study circle with the purpose of exactly this having one hour each week that we meet. One hour every other week for Clean Code book discussions (details in my blog) and one hour every other week for other types of discussions/presentations. I think we see the fruits of this already at our company with a different mindset and more enthusiastic athmosphere.

No man is an island.

PS. How do you measure code quality? Are there any good advices to get here?

]]>