My-Log
| |
| |
|
| |
| |
|
I fell the same way as this person who wrote this peace! Bob Mercer..................
http://webster.cs.ucr.edu/ By Randell Hyde..........................................
The production of high-performance personal computers over the past two decades has enabled the creation of some amazing
software products. However, a common complaint users have with modern software is "despite the fact that machines have gotten
faster, software seems to be getting slower." A large part of this problem is that programmers are no longer challenged to produce
quality applications. High-performance computer systems allow programmers to get away with writing sloppy code and still achieve
an acceptable performance level. There are two problems with this approach:
* Programmers, rather than users (and purchasers of computer systems), are the beneficiaries of improvements in computer architecture.
Faster CPUs allow programmers to write sloppier code while still maintaining the performances levels acceptable on previous generation CPUs.
* Programmers who don't have to work at writing great code, never learn how to write great code (or if they originally knew, their skills atrophy from disuse).
A huge problem today is that many programmers have grown up with high-performance machines and have never learned how to
write decent code in the first place. Unfortunately, advances in computer architecture are no longer doubling CPU performance every
couple of years as they have in the past. Therefore, today's programmers can no longer get away with writing slow code and expecting
advances in computer architecture to rescue them a few years hence.
The Write Great Code series is intended to help rectify this problem by teaching the forgotten art of crafting well-designed, efficient, software.
# # #
I fell the same way as this person who wrote this peace! Bob Mercer..................
http://webster.cs.ucr.edu/ By Randell Hyde..........................................
The production of high-performance personal computers over the past two decades has enabled the creation of some amazing
software products. However, a common complaint users have with modern software is "despite the fact that machines have gotten
faster, software seems to be getting slower." A large part of this problem is that programmers are no longer challenged to produce
quality applications. High-performance computer systems allow programmers to get away with writing sloppy code and still achieve
an acceptable performance level. There are two problems with this approach:
* Programmers, rather than users (and purchasers of computer systems), are the beneficiaries of improvements in computer architecture.
Faster CPUs allow programmers to write sloppier code while still maintaining the performances levels acceptable on previous generation CPUs.
* Programmers who don't have to work at writing great code, never learn how to write great code (or if they originally knew, their skills atrophy from disuse).
A huge problem today is that many programmers have grown up with high-performance machines and have never learned how to
write decent code in the first place. Unfortunately, advances in computer architecture are no longer doubling CPU performance every
couple of years as they have in the past. Therefore, today's programmers can no longer get away with writing slow code and expecting
advances in computer architecture to rescue them a few years hence.
The Write Great Code series is intended to help rectify this problem by teaching the forgotten art of crafting well-designed, efficient, software.
# # #
The production of high-performance personal computers over the past two decades has enabled the creation of some amazing software products. However, a common complaint users have with modern software is "despite the fact that machines have gotten faster, software seems to be getting slower." A large part of this problem is that programmers are no longer challenged to produce quality applications. High-performance computer systems allow programmers to get away with writing sloppy code and still achieve an acceptable performance level. There are two problems with this approach:
A huge problem today is that many programmers have grown up with high-performance machines and have never learned how to write decent code in the first place. Unfortunately, advances in computer architecture are no longer doubling CPU performance every couple of years as they have in the past. Therefore, today's programmers can no longer get away with writing slow code and expecting advances in computer architecture to rescue them a few years hence. The Write Great Code series is intended to help rectify this problem by teaching the forgotten art of crafting well-designed, efficient, software. http://webster.cs.ucr.edu/ THIS is the PLACE! | |||||
Notice
to Bulk E-mailers!
Pursuant to US Code, Title 47, Chapter 5, Sub chapter II, p.227, any
and all unsolicited commercial or none commercial e-mail sent to this address or any e-mail address
that apeareas in this site is subject
to a download and archival fee in the amount of $500 US per incident. Anyone who
sends unsolicited commercial or none commercial e-mail to this account or any e-mail address that
apeareas in this site will be charged a
$500 proofreading fee per incident. Consider this official notification. Failure
to abide by this will result in legal action.
Comments to: rhmercer@rhmercer.org
Notice
to Bulk E-mailers!
Pursuant to US Code, Title 47, Chapter 5, Sub chapter II, p.227, any
and all unsolicited commercial or none commercial e-mail sent to this address or any e-mail address
that apeareas in this site is subject
to a download and archival fee in the amount of $500 US per incident. Anyone who
sends unsolicited commercial or none commercial e-mail to this account or any e-mail address that
apeareas in this site will be charged a
$500 proofreading fee per incident. Consider this official notification. Failure
to abide by this will result in legal action.
Comments to:
href="mailto:rhmercer@rhmercer.org">rhmercer@rhmercer.org
style="background: rgb(255, 255, 0) none repeat scroll 0% 50%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial;">