4 Kicks

Quantity Always Trumps Quality(codinghorror.com)

submitted by spoulsonspoulson(327) 3 years, 9 months ago

When it comes to software, the same rule applies. If you aren't building, you aren't learning. Rather than agonizing over whether you're building the right thing, just build it. And if that one doesn't work, keep building until you get one that does.

2 comments |category: |Views: 5

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
SQL_MenaceSQL_Menace(4890) - mdoppmdopp(856) - yesthatmcgurkyesthatmcgurk(4063) - spoulsonspoulson(327)
Comments:

posted by wisemxwisemx(8074) 3 years, 9 months ago 0

Hey guys...I have studied Quality methods for years.
Designed Q.C. methods for both Ford and Mazda. U.S. and Japan.
In my own seasoned opinion this article is very bad advice.
Quality should be used before, during and after.
PDCA: Plan, Do, Check and Action.

Reply

posted by yesthatmcgurkyesthatmcgurk(4063) 3 years, 9 months ago 0

On the other side, practice makes perfect. I think (like most things) it should be a mix of the two. Take writing, for instance. You can't study your way into being a good writer; you have to write, critique, and improve your writing. However, without reading examples of quality writing and learning from it your progress will be much slower...

Reply

information Login or create an account to comment on this story
Submit a Story
View upcoming stories
How else can I help?
Add our feeds to your site

Most Active Users

What's this?