I'm proudest when I fix a tough bug. Writing code is largely a matter of imagination and syntax, but bug hunting is serious analytical work. I get a rush everytime I nab a really nasty one. It doesn't seem to matter if I'm the one that wrote the buggy code, which I suppose qualifies as stupid!
Lately I've been thinking about another kind of Stupid Emotional Programmer Attachment - the attachment to a favorite language. As the freak that wrote a Perl SDK for Quake 3, I know all about choosing the wrong tool for the job. I've been reading about 3d game programming again and I just can't stop thinking about doing it with Perl. That's just plain dumb. First, Perl performance simply not up to the task. And more importantly, I can learn a lot more from the tons of high quality C/C++ 3d game code if I'm working in the same environment instead of hacking around in an SDL.pm backwater. Smarten up, me!
-sam
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.