|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Diomidis Spinellis, "Job Security," IEEE Software, vol. 26, no. 5, pp. 14-15, September/October, 2009. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2009.131, author = {Diomidis Spinellis}, title = {Job Security}, journal ={IEEE Software}, volume = {26}, number = {5}, issn = {0740-7459}, year = {2009}, pages = {14-15}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.131}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Job Security IS - 5 SN - 0740-7459 SP14 EP15 EPD - 14-15 A1 - Diomidis Spinellis, PY - 2009 KW - job security KW - maintainability KW - analyzability KW - coupling KW - stability KW - testability KW - design KW - software engineering VL - 26 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2009.131
Some consider unmaintainable code a tool that provides job security. At the low level, you can obtain such code through incorrect or inconsistent formatting, naming, and commenting. Complex and gratuitous coupling, lack of assertions, and failure to use a language's type system can further complicate the picture. At a higher level, deep and wide class hierarchies, lack of cohesion, and unhelpful package relationships can hinder maintainability. Finally, at the development process level, lack of version control, subpar build-and-release procedures, a lacking testing infrastructure, and the hiring of mediocre developers will hammer the last nails into a project's maintainability coffin.
Index Terms:
job security, maintainability, analyzability, coupling, stability, testability, design, software engineering
Citation:
Diomidis Spinellis, "Job Security," IEEE Software, vol. 26, no. 5, pp. 14-15, Sept.-Oct. 2009, doi:10.1109/MS.2009.131
Usage of this product signifies your acceptance of the Terms of Use.

