General

TwitterFacebook
Get flash to fully experience Pearltrees
10. Comments explaining “what”, but not “why” Introductory-level programming courses teach students to comment early and often. And while this may be a useful practice during programming infancy (when even the simplest line of code can be incomprehensible), many programmers never bother to shake the habit. http://www.kevinwilliampang.com/2008/08/28/top-10-things-that-annoy-programmers/

Top 10 Things That Annoy Programmers | Kevin William Pang

http://blogs.construx.com/blogs/stevemcc/archive/2007/12/12/technical-debt-decision-making.aspx

Technical Debt Decision Making - 10x Software Development

Steve McConnell said: December 18, 2007 12:47:PM Kevin, You might check out some of the examples of technical debt from my first post on the topic. Here's another example that illustrates the answers to many of your questions. Let's say that you're developing a large app that requires, among other things, 5 reports.
http://www.joelonsoftware.com/articles/fog0000000043.html

The Joel Test: 12 Steps to Better Code

by Joel Spolsky Wednesday, August 09, 2000 Have you ever heard of SEMA ? It's a fairly esoteric system for measuring how good a software team is. No, wait! Don't follow that link!
http://www.codinghorror.com/blog/2006/08/the-programmers-bill-of-rights.html August 24, 2006 It's unbelievable to me that a company would pay a developer $60-$100k in salary, yet cripple him or her with terrible working conditions and crusty hand-me-down hardware. This makes no business sense whatsoever. And yet I see it all the time. It's shocking how many companies still don't provide software developers with the essential things they need to succeed. I propose we adopt a Programmer's Bill of Rights , protecting the rights of programmers by preventing companies from denying them the fundamentals they need to be successful.

The Programmer's Bill of Rights