News for hackers. Stuff that matters.
Re:I'm not sure you've really got this whole Object-Oriented... by zeteo on Saturday September 04, 2010 @10:53AM (#1662785)
It's funny because it's true. How does a manager evaluate the work of his subordinate programmers (especially when the manager is a so-so programmer himself)?

1. Count the lines of code.

2. Randomly inspect code sections.

The verbose Bureaucratese sampled in the article responds to both requirements.

Re:I'm not sure you've really got this whole Object-Oriented... by miguelpais on Saturday September 04, 2010 @11:13AM (#1662818)
Instead of code inspection, maybe the manager should impose short and easy to validate requirements (sub requirements of the general requirements imposed by the client) and ask the programmer to show the software passing them.

Even if TDD is not being used, the programmer can write a simple test for it and then show the manager the test succeed.

This semester I had a class of Software Engineering when we did a project using Scrum and weekly we had to show our teacher that we had accomplished our tasks. The teacher was playing the role of someone who didn't know any code, but we still had to show stuff working. So we would write simple tests to show for instance that SOAP Messages were being sent by one entity and in fact received by the other.

Re:I'm not sure you've really got this whole Object-Oriented... by zeteo on Saturday September 04, 2010 @11:33AM (#1662850)
Oh, it's a bad thing and there are much better ways to evaluate code. But it's done nevertheless.
Re:I'm not sure you've really got this whole Object-Oriented... by eru on Saturday September 04, 2010 @11:10AM (#1662811)
How about cutting the first one, and only going with the second. Knuth used to read a few random pages in depth to grade student papers.