<?xml version="1.0" encoding="windows-1252"?>
<node id="132133" title="Re: (Ovid) Re: Re: (OT) Where is programming headed?" created="2001-12-14 22:47:35" updated="2005-07-19 14:08:11">
<type id="11">
note</type>
<author id="31739">
Rudif</author>
<data>
<field name="doctext">
[Ovid,]&lt;p&gt;
Pardon me if my answer was slightly on the flippant side. What I did want to suggest is that there is continuity between the K&amp;R C and today's C++ classes, objects, templates, containers, iterators, algorithms, and the like. So, if you feel like C/C++ is written in your future, just take it from where you stopped a few years ago and go for it. Same as you do when you go to tackle some tough job in Perl.&lt;p&gt;
Where I [http://www.lecroy.com|work], when we interview programmers for jobs, this is what we look for &lt;br&gt;
- the domain knowledge and experience : software for sci/eng measuring instruments &lt;br&gt;
- the programming experience : C++, real time, component software &lt;br&gt;
- the person : do you have courage and curiosity, can you identify and solve problems, 
 can you find nuggets of knowledge wherever they hide - your head, books, vendor doc (yes!), web;
 do you know the hardships and joys of teamwork? &lt;br&gt;
Knowledge and experience are minimal conditions, personal qualities are decisive.&lt;p&gt;
If you meet a prospective employer who is not probing for these qualities, you should probably look around for another one.&lt;p&gt;

[Rudif]
</field>
<field name="root_node">
131789</field>
<field name="parent_node">
131839</field>
</data>
</node>
