Linked by Thom Holwerda on Thu 6th Sep 2012 21:32 UTC, submitted by MOS6510
Permalink for comment 534230
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2006-12-15
The whole point is and he is right, is that extra performance really worth the extra development time?
If it isn't then it isn't worth it, it is a trade off that should be considered part of the development process.
There's always the question if the extra performance is really worth the time. That's for everyone to decide, their business, not mine. But sometimes it's too late to optimize.
A lot of people in software development forget about the psychological impact of the work that developers do. You might think that there's no impact, but please, think about it one more time.
Give a senior developer menial tasks, and you shall have a mediocre experienced developer. Remember, a developer is as good as the job he does, not as the time he invested into the job.
No, I'm not talking about 'the clever way' to hell. I'm talking about skipping some of the essentials. People that never done a delete nor ever thought about memory consumption will have a hard time when such limits comes into place. I recently had a wtf moment, when someone was caching an entire table in memory, then copying the cache as a backup. His verdict was "sometimes it crashes, don't know why". There's a 'too stupid' too, not only 'too clever'.