Thursday, June 14, 2007

Beware...

Reading this might break your monitor.

Monitors and coffee do not mix, so be careful out there.

Abject Programming - I love it.  My favorite bit:

Documentation

It’s said that code should be written for people to read, so it follows that documentation is written for no one to read. Documentation should be written for every new module and then maintained as changes are put into production, or at least the next time there’s a lull in the workload.

A good time to write documentation is when someone in the department gives two-weeks notice: use that time to make sure the departing team member documents all of their code.

Cluttering up the source code with lots of comments explaining what the code is trying to do is distracting and slows down the compiler. That’s why abject shops that follow “best practices” keep documentation in a document management system where programmers can’t accidentally delete it.

 

That article deserves a bookmark... 

POST A COMMENT

8 Comments:

Blogger Noons said....

LOL! What a great find.
It should come with a big health warning as well!

Thu Jun 14, 11:16:00 PM EDT  

Anonymous Anonymous said....

Well written. On the serious side I would like to read your opinion on agile programming and alike, in particular agile modeling and its suggestions for database refactoring.

Fri Jun 15, 03:18:00 AM EDT  

Blogger Stew said....

This comment has been removed by the author.

Fri Jun 15, 08:08:00 AM EDT  

Blogger Stew said....

Clearly the creator of this methodology is a former programmer from my shop and has stolen our well-used techniques! He's taken hundreds of thousands of lines of code and codified them into a clear, concise methodology for enabling job security for the current programmers, since the barrier for newbies learning our methods kept management from dreaming of replacing us. But these simple methods that took us years to craft would enable anyone to take our jobs away!

Our lawyers will be contacting him to file a cease-and-desist order immediately! :-)

Fri Jun 15, 08:11:00 AM EDT  

Blogger Paul Moore said....

I liked the database design hints in the comments: "You just need the Publishing_Object table with 50 text columns. That’s good scalability best practice." What more can you say? :-)

Fri Jun 15, 08:12:00 AM EDT  

Anonymous Robert Lockard said....

I think I worked there once. Ummm, oh yea, they fired me when I gave a copy of your book "Effective Oracle By Design" to the Tech. Lead.

True Story. One of those places where you go in praying you will be fired.

Later,
-Rob

Fri Jun 15, 09:42:00 AM EDT  

Anonymous Sokrates said....

that was really funny !
making my day !

"... the number of lines a programmer can produce in a day, week, or month is a useful metric for project planning and resource allocation ..."

sad enough that this is really what software team leaders learn at university
sad enough that most of the article
is so true !

Fri Jun 15, 12:26:00 PM EDT  

Anonymous Leo Mannhart said....

"You just need the Publishing_Object table with 50 text columns. That’s good scalability best practice." What more can you say? :-)

hhmmm why 50 text columns? wouldn't it be good practice to have it in 1 (clob) column and have a XML-file with the description what column in the clob means what. Isn't XML nowadays a "must have" ?

Thu Jun 21, 10:16:00 AM EDT  

POST A COMMENT

<< Home