Programming Quotes
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Actually the best way to lose weight is not to weigh yourself at all :D Good quotes - this one's good: ------------------- The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. - Tom Cargill -------------------
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
~ Web SQL Utility: query Access, SQL server, MySQL. Stores history, favourites.
-
Actually the best way to lose weight is not to weigh yourself at all :D Good quotes - this one's good: ------------------- The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. - Tom Cargill -------------------
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
~ Web SQL Utility: query Access, SQL server, MySQL. Stores history, favourites.
Ashley van Gerven wrote:
Good quotes - this one's good: ------------------- The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. - Tom Cargill -------------------
It think it would be something: The first 90% of the code accounts for the first 10% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. Isn't it? :)
Best Regards, Apurva Kaushal
-
Ashley van Gerven wrote:
Good quotes - this one's good: ------------------- The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. - Tom Cargill -------------------
It think it would be something: The first 90% of the code accounts for the first 10% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. Isn't it? :)
Best Regards, Apurva Kaushal
Apurva Kaushal wrote:
the first 10% of the development time. The remaining 10%
That would be 10% + 10%. It was more a joke about how you can write a ton of code up front and fast, but when times comes to start fixing bugs, maintaining software quality, writing tests, etc. another huge effort is required. At least, that's my take on that one.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Apurva Kaushal wrote:
the first 10% of the development time. The remaining 10%
That would be 10% + 10%. It was more a joke about how you can write a ton of code up front and fast, but when times comes to start fixing bugs, maintaining software quality, writing tests, etc. another huge effort is required. At least, that's my take on that one.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
That is quite true it was kinda type of joke only. But that is a fact that developing something really takes less time than debugging and fixing the bug. :)
Best Regards, Apurva Kaushal
I think that's why there needs to be more effort expended up front in the inital planning and coding. If you don't write high quality code from the start, the time saved by doing it sloppy will only come back to bite you later. Because of this, I've been doing far more careful writing of all new code: planning, documentation, unit tests, all up front. Unit tests and so called test-driven development really do make you think about how it's gonna work before you code it, so that helps out with the planning stage too. The result for us has been fewer bugs at the expense of more time spent up front.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
What a load of crap. If you find the bugs in your code before your customer does then you have a better quality product.
Judah Himango wrote:
don't test more; develop better.
If anyone sayes that to me in a job interview I would kick them straight out the door.
Truth is the subjection of reality to an individuals perception
-
I think that's why there needs to be more effort expended up front in the inital planning and coding. If you don't write high quality code from the start, the time saved by doing it sloppy will only come back to bite you later. Because of this, I've been doing far more careful writing of all new code: planning, documentation, unit tests, all up front. Unit tests and so called test-driven development really do make you think about how it's gonna work before you code it, so that helps out with the planning stage too. The result for us has been fewer bugs at the expense of more time spent up front.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
cent percen true what happens actually is even if you do all sort of planning some crap will still remain and that will cause all the headache in the last moment. But in any case with proper planning 90% of the last moment headache can be removed. :)
Best Regards, Apurva Kaushal
-
cent percen true what happens actually is even if you do all sort of planning some crap will still remain and that will cause all the headache in the last moment. But in any case with proper planning 90% of the last moment headache can be removed. :)
Best Regards, Apurva Kaushal
Absolutely. Planning, good documentation, unit testing, and careful coding will not eliminate bugs. They will, however, decrease the number of bugs, make it easier to fix bugs, and allow you to verify your fixes don't break anything else.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Absolutely. Planning, good documentation, unit testing, and careful coding will not eliminate bugs. They will, however, decrease the number of bugs, make it easier to fix bugs, and allow you to verify your fixes don't break anything else.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
What a load of crap. If you find the bugs in your code before your customer does then you have a better quality product.
Judah Himango wrote:
don't test more; develop better.
If anyone sayes that to me in a job interview I would kick them straight out the door.
Truth is the subjection of reality to an individuals perception
I think the point there is that testing (in particular, unit testing) doesn't make your software better, as some devs seem to think. Instead, testing measures the quality of your code, allowing you to develop it better by refactoring, fixing bugs, designing it better the next iteration.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
What a load of crap. If you find the bugs in your code before your customer does then you have a better quality product.
Judah Himango wrote:
don't test more; develop better.
If anyone sayes that to me in a job interview I would kick them straight out the door.
Truth is the subjection of reality to an individuals perception
McConnell is right in a way but it's not either-or. We should develop better and test more. Both improve quality. A good pointer is this: http://www-users.cs.york.ac.uk/~paige/Writing/xp2004.pdf[^]
Kevin
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Indeed, but Test Driven Development is like weighing yourself immediately before you decide whether (or what) to eat, which is a good way to lose weight.
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. Alan Kay That sounds about right.
:josh: My WPF Blog[^]
-
Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. Alan Kay That sounds about right.
:josh: My WPF Blog[^]
Heheh, agreed. But is he saying there's no structural integrity to Egyptian pyramids? I don't think that's accurate. Anyways, getting off topic now...
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Heheh, agreed. But is he saying there's no structural integrity to Egyptian pyramids? I don't think that's accurate. Anyways, getting off topic now...
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Judah Himango wrote:
But is he saying there's no structural integrity to Egyptian pyramids? I don't think that's accurate
I don't know if the Egyptian pyramids have structural integrity or not. When I read that quote I envisioned rock-dragging slaves being whipped in the hot sun. That just seemed so appropriate an analogy to some software projects! :)
:josh: My WPF Blog[^]
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
The most amazing achievement of the computer software industry is its continuing cancellation of the steady and staggering gains made by the computer hardware industry. - Henry Petroski And here I thought that quote was supposed to be attributed to the Windows Vista team... Oh well...:rolleyes:
Any sufficiently gross incompetence is nearly indistinguishable from malice.
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
Jello bugs[^], by Kent Beck:
I remember hearing a description of the release process at Microsoft and someone likened it to Jello. You got this software and it's like Jello and people are making changes and it’s shaking and it's shaking and you think you're getting close but the software's still shaking and then it stops shaking just for a second and that's when you ship it.
0 bottles of beer on the wall, 0 bottles of beer, you take 1 down, pass it around, 4294967295 bottles of beer on the wall. Awasu 2.2.3 [^]: A free RSS/Atom feed reader with support for Code Project.
-
Programming Quotes Page[^] :cool: My favorite:
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better. Steve McConnell Code Complete
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Dumbest. Movie. Title. Evaaar. The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
One of my favorites and it seems to impress my boss is: If you only have a hammer everything looks like a nail. I suspose this means sometimes people approach a problem from the perspective of what they currently know or have instead of asking what really is the best way.