The worst source code
-
Somewhere I read this in a signature: The worst source code, that you can come across, is the code you wrote on your own one year ago. I just remember this, because I'm sitting in front of some part of my own code that is three or four years old. X| Ok, to see it positive: I learned a lot in the past years.
Markus-811 wrote:
Somewhere I read this in a signature:
thatraja
-
Some of the samples of code that I wrote years ago were things of beauty - they were lean, efficient, mindful of every last clock cycle and optimizer trick that I could employ. It's sad to see how flabby my code ended up becoming with the advent of frameworks - it became too easy to rely on a potentially inefficient API implementation, rather than coding up a tighter implementation of my own.
I can relate. On the other hand, I feel like optimizing code has now become less relevant than transparency.
-
Some of the samples of code that I wrote years ago were things of beauty - they were lean, efficient, mindful of every last clock cycle and optimizer trick that I could employ. It's sad to see how flabby my code ended up becoming with the advent of frameworks - it became too easy to rely on a potentially inefficient API implementation, rather than coding up a tighter implementation of my own.
So now you use a framework, throw a crap load of more cycles at it and produce 5 times as much out the door! I call that a win, if not an elegant win!
Never underestimate the power of human stupidity RAH
-
So now you use a framework, throw a crap load of more cycles at it and produce 5 times as much out the door! I call that a win, if not an elegant win!
Never underestimate the power of human stupidity RAH
Oh, I know - that's the whole reason I use the frameworks in the first place. Sadly, though, the ability to optimise is being squeezed out and it seems as though younger generations of coders don't want to learn how to do this. There are exceptions, obviously, but as these are the coders that go into places like Microsoft, inefficiencies will continue to be propagated,
-
Somewhere I read this in a signature: The worst source code, that you can come across, is the code you wrote on your own one year ago. I just remember this, because I'm sitting in front of some part of my own code that is three or four years old. X| Ok, to see it positive: I learned a lot in the past years.
That is sad and funny at the same time.... :-D :(
There are no secrets to success. It is the result of preparation, hard work, and learning from failure. Colin Powell
-
Some of the samples of code that I wrote years ago were things of beauty - they were lean, efficient, mindful of every last clock cycle and optimizer trick that I could employ. It's sad to see how flabby my code ended up becoming with the advent of frameworks - it became too easy to rely on a potentially inefficient API implementation, rather than coding up a tighter implementation of my own.
-
Shameel wrote:
despite the fact that it was VB6.
Burn the heretic! :laugh:
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
-
OriginalGriff wrote:
Burn the heretic!
That was 15 years ago and people do reform, don't they?
Shameel wrote:
people do reform, don't they?
To reform, they have to show contrition; remorse:
Shameel wrote:
I love my code I wrote 15 years ago
Oops! Burn him! Burn him now!
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
-
Oh, I know - that's the whole reason I use the frameworks in the first place. Sadly, though, the ability to optimise is being squeezed out and it seems as though younger generations of coders don't want to learn how to do this. There are exceptions, obviously, but as these are the coders that go into places like Microsoft, inefficiencies will continue to be propagated,
Pete O'Hanlon wrote:
younger generations of coders don't want to learn how to do this
It so happens that in the past few months I had to look at code from some of my co-workers. I can only confirm that statement. I know I'm considered somewhat of a weird programmer in my company cause I keep going on about performance and will try and squeeze every milliseconde out of my code but the things I'v seen here are just terrifying. - Code that uses 16+ gig ram (for a very simple request) - Code that takes 10+ min to run (to get 200k records) - Horrific linq statements that just screams inefficient. - ... The attention for detail seems to be gone with younger programmers (or less experienced one's), the response I get when I tell them their program can use up to 50% less ram is usually 'we'll just add a few gigs of ram to the server if it's a problem', makes me shiver every time. And yes I know that from your view point I'm probably in that 'younger generation' :) (I'm 30 :) ) perhaps that's what makes me weird ;P
-
Somewhere I read this in a signature: The worst source code, that you can come across, is the code you wrote on your own one year ago. I just remember this, because I'm sitting in front of some part of my own code that is three or four years old. X| Ok, to see it positive: I learned a lot in the past years.
Pfft. I'm still maintaining code I wrote over ten years ago. My worst pain point with it is I was still using K&R braces back then.
Software Zen:
delete this; -
Pete O'Hanlon wrote:
younger generations of coders don't want to learn how to do this
It so happens that in the past few months I had to look at code from some of my co-workers. I can only confirm that statement. I know I'm considered somewhat of a weird programmer in my company cause I keep going on about performance and will try and squeeze every milliseconde out of my code but the things I'v seen here are just terrifying. - Code that uses 16+ gig ram (for a very simple request) - Code that takes 10+ min to run (to get 200k records) - Horrific linq statements that just screams inefficient. - ... The attention for detail seems to be gone with younger programmers (or less experienced one's), the response I get when I tell them their program can use up to 50% less ram is usually 'we'll just add a few gigs of ram to the server if it's a problem', makes me shiver every time. And yes I know that from your view point I'm probably in that 'younger generation' :) (I'm 30 :) ) perhaps that's what makes me weird ;P
-
Pete O'Hanlon wrote:
younger generations of coders don't want to learn how to do this
It so happens that in the past few months I had to look at code from some of my co-workers. I can only confirm that statement. I know I'm considered somewhat of a weird programmer in my company cause I keep going on about performance and will try and squeeze every milliseconde out of my code but the things I'v seen here are just terrifying. - Code that uses 16+ gig ram (for a very simple request) - Code that takes 10+ min to run (to get 200k records) - Horrific linq statements that just screams inefficient. - ... The attention for detail seems to be gone with younger programmers (or less experienced one's), the response I get when I tell them their program can use up to 50% less ram is usually 'we'll just add a few gigs of ram to the server if it's a problem', makes me shiver every time. And yes I know that from your view point I'm probably in that 'younger generation' :) (I'm 30 :) ) perhaps that's what makes me weird ;P
-
Somewhere I read this in a signature: The worst source code, that you can come across, is the code you wrote on your own one year ago. I just remember this, because I'm sitting in front of some part of my own code that is three or four years old. X| Ok, to see it positive: I learned a lot in the past years.
Markus-811 wrote:
The worst source code, that you can come across, is the code you wrote on your own one year ago.
Both of the commas in the sentence are incorrect. If the guy writes code with as many syntax errors, I can well believe his statement.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Pfft. I'm still maintaining code I wrote over ten years ago. My worst pain point with it is I was still using K&R braces back then.
Software Zen:
delete this;Gary R. Wheeler wrote:
My worst pain point with it is I was still using K&R braces back then
Kernighan and Ritchie?! Oh, that is a rather old notation. But if it has a readable architecture/structure, this can still make some fun. But my coding style changed from hacking to something more sophisticated.
