By Topic

Why Johnny can't program [computing professionals]

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
N. Holmes ; Tasmania Univ., Hobart, Tas., Australia

Innumerate, illiterate, and overwhelmed, today's computing professionals ('Johnny') are torn between system design and program coding. Computing professionals must know vastly more now than they needed to know 40 years ago (1960s), but even then the field often distinguished between programmers and systems analysts. Meanwhile, Johnny must know too much to be at the same time a skilled programmer and a skilled system engineer. That is why he's overwhelmed. But Johnny's problem goes deeper. If he wants to be a professional programmer, he must learn on the job. Programmers have few trade courses to select from, many fewer than those available to carpenters, plumbers, and electricians. Further, very few professional courses will assist Johnny if he wants to become a straightforward, generalist, humanist, system engineer. Specialists such as computer system engineers and software engineers appear to dominate the field. No wonder Johnny has a problem. Let's move to give him the proper training to become whichever he wants to be: programmer or system engineer.

Published in:

Computer  (Volume:33 ,  Issue: 12 )