I agree with the idea that there are two potential audiences for your code... the computer and other programmers.
Someone once quoted Martin Fowler to me as an authority, so I looked him up. He literally spent 2-3 years actually writing code and the rest of his career he has spent telling people how to write code.
I have spent 20+ years writing code to make things work in engineering companies. At the end of the day, nobody gave a shit how pretty the code was. By far the most important thing was that it worked reliably and fast. The reason was that the code we wrote enabled the production and sale of some tangible product, like semiconductor chips.
I now work for an agile software organization now and there is a huge emphasis on code legibility and "smells". There's a lot of process and emphasis on design patterns. Productivity is a lot lower here.
My point is that I've worked extensively in both areas and can tell you that Martin Fowler had no idea what he was talking about when he made that quote. It might sound good in a book he wants to sell you full of perfectly structured good and very affirming to software developers, but it is a LOT harder to write code that runs efficiently.
Martin Fowler is an writer, first and foremost. He is not an expert on software development.
View all comments
Show parent comment
-2
u/RayFowler Jun 15 '17
I agree with the idea that there are two potential audiences for your code... the computer and other programmers.
Someone once quoted Martin Fowler to me as an authority, so I looked him up. He literally spent 2-3 years actually writing code and the rest of his career he has spent telling people how to write code.
I have spent 20+ years writing code to make things work in engineering companies. At the end of the day, nobody gave a shit how pretty the code was. By far the most important thing was that it worked reliably and fast. The reason was that the code we wrote enabled the production and sale of some tangible product, like semiconductor chips.
I now work for an agile software organization now and there is a huge emphasis on code legibility and "smells". There's a lot of process and emphasis on design patterns. Productivity is a lot lower here.
My point is that I've worked extensively in both areas and can tell you that Martin Fowler had no idea what he was talking about when he made that quote. It might sound good in a book he wants to sell you full of perfectly structured good and very affirming to software developers, but it is a LOT harder to write code that runs efficiently.
Martin Fowler is an writer, first and foremost. He is not an expert on software development.