Most of the time, yes. Especially in the web development world. However, it does exist. I used to work for a major defense contractor. Our code ran on military aircraft and had to meet very rigid standards for very good reasons. Part of the development process was doing code reviews to make sure the code met those standards. They weren't the type of group code reviews people do to help programmers improve their code, but were one person sitting down going through the code line by line and looking for problems. When doing one of these reviews, I got to a section of code that I indeed considered elegant. Not only that, but I was fairly sure I knew which person did it. When I finished the review, I sought this person out and asked him if he had done it without telling him why I wanted to know. When he confirmed my suspicions, I made sure to compliment him on doing such a great job. Code like his not only passed the review, but would be a joy to maintain. I think a lot of it is the person's mindset.
I think it's great that someone close to the site posted something like this. It could have opened up a wonderful dialog. However, you really diluted your message by adding those last two sentences.
Unfortunately many university libraries are no longer the quiet places to study that they once were. In an attempt to remain relevant, they're doing all kinds of things that make them less than ideal study environments. But, you can certainly try. You might find a quiet corner somewhere.
If you can't be out riding your motorcycle, at least you can enjoy reading about them.
Most of the time, yes. Especially in the web development world. However, it does exist. I used to work for a major defense contractor. Our code ran on military aircraft and had to meet very rigid standards for very good reasons. Part of the development process was doing code reviews to make sure the code met those standards. They weren't the type of group code reviews people do to help programmers improve their code, but were one person sitting down going through the code line by line and looking for problems. When doing one of these reviews, I got to a section of code that I indeed considered elegant. Not only that, but I was fairly sure I knew which person did it. When I finished the review, I sought this person out and asked him if he had done it without telling him why I wanted to know. When he confirmed my suspicions, I made sure to compliment him on doing such a great job. Code like his not only passed the review, but would be a joy to maintain. I think a lot of it is the person's mindset.
I think it's great that someone close to the site posted something like this. It could have opened up a wonderful dialog. However, you really diluted your message by adding those last two sentences.
While I've seen tons of garbage posted here on Slashdot, this one takes the cake.
Unfortunately many university libraries are no longer the quiet places to study that they once were. In an attempt to remain relevant, they're doing all kinds of things that make them less than ideal study environments. But, you can certainly try. You might find a quiet corner somewhere.