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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||