The pyramid of code quality, the 5 characteristics of good code.(makinggoodsoftware.com)
makinggoodsoftware.com
The pyramid of code quality, the 5 characteristics of good code.
http://makinggoodsoftware.com/2009/05/07/the-pyramid-of-code-quality-the-5-characteristics-of-good-code/
7 コメント
I don't mean to single this out in particular, but what's with the articles getting posted with barely a few paragraphs of actual content?
Bill Gates:
“Measuring programming progress by lines of code is like measuring aircraft building progress by weight“.
“Measuring programming progress by lines of code is like measuring aircraft building progress by weight“.
Well, this is an article about programming, not a program, and it's pretty insubstantial. All it really does is mention some buzzwords and and note that they're the foundation of the "pyramid of code quality". Nothing personal against the author, but it's pretty flat for something that's stayed on the front page through evening. I wonder why it's getting voted up.
This article on ssh (http://sigusr2.net/2009/May/07/hacker-utility-belt-ssh.html) barely scratches the surface, too. At the very least, I'd mention ssh-agent (a good intro: http://mah.everybody.org/docs/ssh) and visual fingerprints for host keys (http://gwolf.org/node/1864).
But, I really should be constructive and write something myself, rather than just griping here. It's much easier to complain about other peoples' writing than to write. One of these days...
This article on ssh (http://sigusr2.net/2009/May/07/hacker-utility-belt-ssh.html) barely scratches the surface, too. At the very least, I'd mention ssh-agent (a good intro: http://mah.everybody.org/docs/ssh) and visual fingerprints for host keys (http://gwolf.org/node/1864).
But, I really should be constructive and write something myself, rather than just griping here. It's much easier to complain about other peoples' writing than to write. One of these days...
Hi guys,
Thanks for your comments!!
@Janzert - About the first image, sorry about that, I have just changed to a gif image, now it should be a few kb, thanks for that.
@jhancock - You are right to mention that there is no comment on how to measure any of the vertex, that´s the tricky part, I am going to evolve the idea in future posts and I hope I will be able to provide with some ideas, anyway I think the most important thing is to have in mind the pyramid when developing
@silentbicycle - Sorry if my post is short, I just wanted to share this idea and as I like the articles that are very lean I thought the best was to express it with as less words as possible.
Anyway thanks to everyone for your comments.
Thanks for your comments!!
@Janzert - About the first image, sorry about that, I have just changed to a gif image, now it should be a few kb, thanks for that.
@jhancock - You are right to mention that there is no comment on how to measure any of the vertex, that´s the tricky part, I am going to evolve the idea in future posts and I hope I will be able to provide with some ideas, anyway I think the most important thing is to have in mind the pyramid when developing
@silentbicycle - Sorry if my post is short, I just wanted to share this idea and as I like the articles that are very lean I thought the best was to express it with as less words as possible.
Anyway thanks to everyone for your comments.
Thanks for the smaller image. While it was more of a surprise to me than an annoyance I'm sure all the dial-up users will be much happier with the smaller image.
I am genuinely interested in knowing what tool(s) or possibly sequence of events led to such a poor png generation though.
Can't wait to see future posts expanding on the four legs of the pyramid and measurements thereof. It certainly does seem like an interesting and useful way to think about it.
I am genuinely interested in knowing what tool(s) or possibly sequence of events led to such a poor png generation though.
Can't wait to see future posts expanding on the four legs of the pyramid and measurements thereof. It certainly does seem like an interesting and useful way to think about it.
Gah, can someone explain how the first png in the article (pyramid.png) came to be well over 1 megabyte? Simply opening it and resaving in gimp brings it down to 83kb and running it through optipng will bring it down to 45kb.
"The apex of the pyramid measures how many things the code does, and how reliable it is."
This is at the end of the article as the 5th "vertex". Nothing more on this. The approach is interesting but without clear understanding of how you measure this 5th vertex or how you contain the other 4 while scaling into the 5th, you have a half-baked pyramid.
This is at the end of the article as the 5th "vertex". Nothing more on this. The approach is interesting but without clear understanding of how you measure this 5th vertex or how you contain the other 4 while scaling into the 5th, you have a half-baked pyramid.