|
Marc Clifton wrote: we developers really don't give a damn about them either.
Leave alone the full-fledged documentation at least the developers should get into the habit of writing at least a one-line comment for the methods to save the posterity and they should cultivate the habit of refraining from commenting code blocks and depend on source control for saving alternate implementations.
A tougher enforcement besides a corporal punishment to the manager heading such a developer alone would bring a good discipline.
Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips
The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!
|
|
|
|
|
Vasudevan Deepak Kumar wrote: they should cultivate the habit of refraining from commenting code blocks and depend on source control for saving alternate implementations
oh how i wish this would happen.
|
|
|
|
|
|
Where I'm at, there is a separate test and documentation team. That said, unit tests and inline code documentation is in the realm of the dev, just considered part of normal development work, and it is not called out specifically.
-----
In the land of the blind, the one eyed man is king.
|
|
|
|
|
basically
i am woring with a small organization, mostly i am cleaning up the debris of those who went before.
it is obvious in the IT organisations, new Developer not agree with the old code developed by the peoples who leaves the industries....
always he is tring to optimize or make changes in that code..
and try to prove he is better than old developer
what a FUN.... 
regards
koolprasad2003
Rating alway..... WELCOME
Be a good listener...Because Opprtunity knoughts softly...N-Joy
|
|
|
|
|
I try to never judge the code that came before I did.
If it wasn't for that code, however crude it may seem, I might not have had a job, or even worse, this company might have not existed.
In our company, the original software system was written in 1 week. It was barely functional at the time, but enough to secure the contract that ended up fueling our organization for years to come.
Today, 9 years later, we are re-writing it with a team of developers. Always respecting the original coder(s) for brilliant "survival-coding" (if I may coin it) techniques.
|
|
|
|
|
Well said. In my younger days I also used to be quick to judge other developers' code. These days I don't any more.
We do not always know the circumstances in which the software was developed. It could have been in a very short period of time, as you mentioned. It could have been that due to financial constraint they had to employ a junior developer that was still learning. It could simply have been that the development tools wereen't up to the task.
We have all written crappy code in our lives, some of which we used to defend vigorously against any kind of criticism. I like to think of my self as a developer with 15 years of experience that can still learn a lot from his peers regardless of seniority.
Ego non sum semper iustus tamen Ego sum nunquam nefas!
|
|
|
|
|
evilnoodle wrote: the original software system was written in 1 week
That's called a Proof Of Concept (POC) and they are often used to sell the idea to the client. It's when that POC becomes the core of the solution that I cringe.
I once spent 3 months writing a solution and a year later they had a team of 20 rewrite it to company specification. It ended up slower and more difficult to use and maintain but the client was happy as it conformed to their standards.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
