My company has two teams, knowledge engineers and software engineers. The knowledge engineers build prototypes in either Lisp or Perl which are eventually transformed into efficient C/C++ code by the software engineers.
Usually I try to keep in mind that someone has to port my code at some stage, so I tend to avoid writing code that is too Perlish. Of course it happens that I forget and start using Perl idioms that are more difficult to translate.
Currently one of the software engineers is porting a particular piece of code which is simple in Perl, but non-trivial in C. Realizing this I asked him whether it was not too hard and his answer was pretty nice: "Well, each statement is a bit of a challenge, but understanding it prepares me for the next one, which is just a bit harder."
Note that our software engineers are very good at their job (and none read PerlMonks).
Just something from daily experience, -gjb-
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||