|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
Yet Another Optimization Article
May/June 2002 (vol. 19 no. 3)
pp. 20-21
| ASCII Text | x | ||
| Martin Fowler, "Yet Another Optimization Article," IEEE Software, vol. 19, no. 3, pp. 20-21, May/June, 2002. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2002.1003448, author = {Martin Fowler}, title = {Yet Another Optimization Article}, journal ={IEEE Software}, volume = {19}, number = {3}, issn = {0740-7459}, year = {2002}, pages = {20-21}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2002.1003448}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Yet Another Optimization Article IS - 3 SN - 0740-7459 SP20 EP21 EPD - 20-21 A1 - Martin Fowler, PY - 2002 VL - 19 JA - IEEE Software ER - | |||
For many programmers, performance is something you pay continuous attention to as you program. Every time you write fragment of code, you consider the performance implications and code the program to maximize performance. This is an obvious technique--pity it works so badly.
Citation:
Martin Fowler, "Yet Another Optimization Article," IEEE Software, vol. 19, no. 3, pp. 20-21, May-June 2002, doi:10.1109/MS.2002.1003448
Usage of this product signifies your acceptance of the Terms of Use.