Comments on: Why good programmer never write good programs

By: Johnny

Johnny — Tue, 21 Feb 2012 10:33:43 +0000

What a great analysis! No idea how you wrote this text..it’d take me days. Well worth it though, I’d assume. Have you considered selling advertising space on your website?

By: Volta - typed JS? | Tamir Khason - Just code

Volta - typed JS? | Tamir Khason - Just code — Thu, 01 Jan 2009 09:10:54 +0000

[...] cool, however, while web development trying to escape variable types, client side development trying to get into it. Isn’t is [...]

By: ekampf

ekampf — Thu, 01 Jan 2009 08:29:37 +0000

There's a difference between "designing a product" which requires customers input, UX input etc. to make it usable and to the needs of the users and "writing a product" which is the next step and requires product to be written with the right tools for the right job, scale, globalize, etc.

So I have to disagree, good programmers can write good programs.

I also disagree with a good programmer described as "He always in new technologies and applies them in his everyday work".

A good experienced programmer knows how to apply the right tool for the right job, not the new tool for a job.

Just see Twitter as an example of programmers using Ruby to build a website only to discover Ruby doesn't scale well..

By: ekampf

ekampf — Thu, 01 Jan 2009 08:29:36 +0000

Hi Tamir,

I'm afraid I have to disagree.

There's a difference between "writing a program" and a "designing a product" and while the stage of product design requires PMs and UX to understand customer needs and provide the best solution, the implementation stage requires good coding methodologies, the use of the right tools and technologies etc.

Writing a good program means that it anwers requirements, correctly structured, scales, globalizeable, etc.

However, the excellent programmer will also have the bussiness skills, UX skills and knowledge in multiple not necessarily technical areas that will help him understand requirements better and communicated with PM\UX\etc. better.

I also have to disagree with defining a good programmer as "He always in new technologies and applies them in his everyday work".

A good programmer knows how to apply the right tool\technology to the right problem and not get caught in in hypes etc.

Just as a case study you can look a Twitter who used Ruby to develop their web site only to find out Ruby doesn't scale well...

Eran.

By: Asafs

Asafs — Thu, 01 Jan 2009 08:29:35 +0000

I think that the problem here is that what is called “good programming” is the aftereffect that this has on the customer. Although the customer doesn’t care about the bits and bytes of the source code, he does care about quick resolution of problems and future enhancements to the product. Writing the best code ever make take its toll in this since the source code is not always maintained by the same developer.

By: Tamir Khason

Tamir Khason — Thu, 01 Jan 2009 08:29:34 +0000

Eran, the problem is, that very small amount of companies, realizes "the right way". Even, if they are, they are not accomplish "customer oriented design" as very important stage.

A lot of complanies some day comes to the stage, when they want programmers to continue to work with clients, wich completely wrong.

By: Yochay Kiriaty

Yochay Kiriaty — Thu, 01 Jan 2009 08:29:33 +0000

Thanks to Alik , I got to read this post from the PowerShell Team . IBM Releases PowerShell Cmdlets to

By: Just code - Tamir Khason

Just code - Tamir Khason — Thu, 01 Jan 2009 08:29:31 +0000

Recently, Microsoft released Violta . This is kind of framework, that using .NET to emit client side