Skip to main content
Software Engineering

Return to Answer

Copy edited. (its = possessive, it's = "it is" or "it has". See for example <http://www.wikihow.com/Use-Its-and-It%27s>.)
Source Link
Peter Mortensen
Peter Mortensen
  • 1k
  • 2
  • 12
  • 15

Honestly it depends. I like how everyone spouts the party line about how "anything less than clean well documented code is a sheer travesty!", but I work in a business with ridiculous deployment cycles and zero oversiteoversight: I do the best I can, but I write so much code itsit's extremely difficult to write the clean perfect code that everyone else claims they write.

What I try to do is write code that can be easily maintained by someone who has roughly my ability. I comment the tricky parts, I name the programs, variables, and classes friendly names, I deploy, and I move on. I don't have time to do anything else.

Sometimes I feel a bit guilty about it, but not very. You should see some of the horrors I deal with on a daily basis. Decades of custom code in obscure languages with zero documentation. One of my coworkers develops exclusively in VB6Visual Basic 6.0 and deploys cryptically named binaries all over the place. The woman I replaced programmed exclusively in RPG.

It's just extremely difficult for me to believe, as much horrible crap as I've seen in my years as a programmer, that everyone only generates clean code.

Honestly it depends. I like how everyone spouts the party line about how "anything less than clean well documented code is a sheer travesty!" but I work in a business with ridiculous deployment cycles and zero oversite: I do the best I can, but I write so much code its extremely difficult to write the clean perfect code that everyone else claims they write.

What I try to do is write code that can be easily maintained by someone who has roughly my ability. I comment the tricky parts, I name the programs, variables, and classes friendly names, I deploy, I move on. I don't have time to do anything else.

Sometimes I feel a bit guilty about it, but not very. You should see some of the horrors I deal with on a daily basis. Decades of custom code in obscure languages with zero documentation. One of my coworkers develops exclusively in VB6 and deploys cryptically named binaries all over the place. The woman I replaced programmed exclusively in RPG.

It's just extremely difficult for me to believe, as much horrible crap as I've seen in my years as a programmer, that everyone only generates clean code.

Honestly it depends. I like how everyone spouts the party line about how "anything less than clean well documented code is a sheer travesty!", but I work in a business with ridiculous deployment cycles and zero oversight: I do the best I can, but I write so much code it's extremely difficult to write the clean perfect code that everyone else claims they write.

I try to write code that can be easily maintained by someone who has roughly my ability. I comment the tricky parts, I name the programs, variables, and classes friendly names, I deploy, and I move on. I don't have time to do anything else.

Sometimes I feel a bit guilty about it, but not very. You should see some of the horrors I deal with on a daily basis. Decades of custom code in obscure languages with zero documentation. One of my coworkers develops exclusively in Visual Basic 6.0 and deploys cryptically named binaries all over the place. The woman I replaced programmed exclusively in RPG.

It's just extremely difficult for me to believe, as much horrible crap as I've seen in my years as a programmer, that everyone only generates clean code.

Post Made Community Wiki by Benjamin Wootton
Source Link
Satanicpuppy
Satanicpuppy
  • 6.2k
  • 26
  • 28

Honestly it depends. I like how everyone spouts the party line about how "anything less than clean well documented code is a sheer travesty!" but I work in a business with ridiculous deployment cycles and zero oversite: I do the best I can, but I write so much code its extremely difficult to write the clean perfect code that everyone else claims they write.

What I try to do is write code that can be easily maintained by someone who has roughly my ability. I comment the tricky parts, I name the programs, variables, and classes friendly names, I deploy, I move on. I don't have time to do anything else.

Sometimes I feel a bit guilty about it, but not very. You should see some of the horrors I deal with on a daily basis. Decades of custom code in obscure languages with zero documentation. One of my coworkers develops exclusively in VB6 and deploys cryptically named binaries all over the place. The woman I replaced programmed exclusively in RPG.

It's just extremely difficult for me to believe, as much horrible crap as I've seen in my years as a programmer, that everyone only generates clean code.