Ovid,
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&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.
Where I work, when we interview programmers for jobs, this is what we look for
- the domain knowledge and experience : software for sci/eng measuring instruments
- the programming experience : C++, real time, component software
- 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?
Knowledge and experience are minimal conditions, personal qualities are decisive.
If you meet a prospective employer who is not probing for these qualities, you should probably look around for another one.
Rudif
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|