McConnell, S. (1998) Why you should use routines..routinely. IEEE Software, 15 (4) 96-95 doi:10.1109/52.687957

Library Home Bookshelves View by Type Using Search

Books Catalogs/Sales Lists Journals Reports Thesis/Dissertation

Search for Books Search for Journals Manage Subjects Statistics Books without DDC/LCC Top Unstructured Orphaned Articles

Bookshelves (DDC layout)Bookshelves (LCC layout)Latest Books

Advanced

Search inside 'IEEE Software' only

- Only viewable:

Reference Type	Journal (article/letter/editorial)
Title	Why you should use routines...routinely
Journal	IEEE Software
Authors	McConnell, S.		Author
Year	1998	Volume	15
Issue	4
Publisher	Institute of Electrical and Electronics Engineers (IEEE)
DOI	doi:10.1109/52.687957Search in ResearchGate
	Generate Citation Formats
Mindat Ref. ID	15420149	Long-form Identifier	mindat:1:5:15420149:4
GUID	0
Full Reference	McConnell, S. (1998) Why you should use routines..routinely. IEEE Software, 15 (4) 96-95 doi:10.1109/52.687957
Plain Text	McConnell, S. (1998) Why you should use routines..routinely. IEEE Software, 15 (4) 96-95 doi:10.1109/52.687957
In	(1998, July) IEEE Software Vol. 15 (4) Institute of Electrical and Electronics Engineers (IEEE)

	*Furey, S. (1997) Why we should use function points [software metrics]. IEEE Software, 14 (2) 28 doi:10.1109/52.582971*
	*Zvegintzov, N. (1998) Software should live longer. IEEE Software, 15 (4) 19 doi:10.1109/52.687939*
	*McConnell, S. (1998) Problem programmers. IEEE Software, 15 (2) 128 doi:10.1109/52.663801*
	*McConnell, S. (1998) Feasibility studies. IEEE Software, 15 (3) 120 doi:10.1109/52.676989*
	*Schneidewind, N.F. (1998) Professional Organizations Should Define Standards. IEEE Software, 15 (6) 96-98 doi:10.1109/ms.1998.730856*
	*McConnell, S. (1998) The art, science, and engineering of software development. IEEE Software, 15 (1) 120-119 doi:10.1109/52.646892*
	*Zucconi, L. (1998) Standards should be defined by a cross-section of the software industry. IEEE Software, 15 (6) 94-96 doi:10.1109/ms.1998.730855*
	*Robertson, J. (2002) Eureka! Why analysts should invent requirements. IEEE Software, 19 (4) 20-22 doi:10.1109/ms.2002.1020281*
	*Yamaura, T. (1998) Why Johnny can't test [software]. IEEE Software, 15 (2) 113-115 doi:10.1109/52.663795*
	*Fowler, M. (2003) Data access routines. IEEE Software, 20 (6) 96-98 doi:10.1109/ms.2003.1241375*
	*Kariya, S. (2002) "So why should we hire you?" [interview techniques]. IEEE Spectrum, 39 (2) 68-71 doi:10.1109/6.991302*

Mindat.org is an outreach project of the Hudson Institute of Mineralogy, a 501(c)(3) not-for-profit organization.
Copyright © mindat.org and the Hudson Institute of Mineralogy 1993-2025, except where stated. Most political location boundaries are © OpenStreetMap contributors. Mindat.org relies on the contributions of thousands of members and supporters. Founded in 2000 by Jolyon Ralph.
To cite: Ralph, J., Von Bargen, D., Martynov, P., Zhang, J., Que, X., Prabhu, A., Morrison, S. M., Li, W., Chen, W., & Ma, X. (2025). Mindat.org: The open access mineralogy database to accelerate data-intensive geoscience research. American Mineralogist, 110(6), 833–844. doi:10.2138/am-2024-9486.
Privacy Policy - Terms & Conditions - Contact Us / DMCA issues - Report a bug/vulnerability Current server date and time: August 31, 2025 11:05:51

Go to top of page

McConnell, S. (1998) Why you should use routines..routinely. IEEE Software, 15 (4) 96-95 doi:10.1109/52.687957

See Also