The correct answer should be "I don't know yet." I've been writing code for almost 40 years now (quite a trick given that I'm only 39!) and have lost count of the number of languages and psuedo-languages I've learned over the years. What I do know is this - whenever I try to learn, or learn about, some new language just for jollies or for some poorly-defined future need, it doesn't take. If I ever do use the language, I pretty much have to start over. Best practice is that you learn a new language when you have need of it, either for development or for understanding some piece of code you've inherited and now must maintain. This may lead to some steep learning curves that must be surmounted in a short period of time, but nothing focuses the old brain like "learn this or die." I keep track of what's out there, but I've given up on dabbling in a new language until I have need to.
One possible exception to this is learning new paradigms. For example, for all us old dinosaur linear-language programmers, OO design and development was a bit of a stretch. It was useful to learn the precepts and concepts of OO programming before actually needing it (I fought with both C++ and Ada as OO learning platforms before finally learning Java WHEN I NEEDED TO). But learning a new language just to add another type of screwdriver to the old toolbox is just not productive. It also takes time away from drinking beer. Jim *---------------------*-------------------------------* | Jim Secan | Northwest Research Assoc, Inc | | ([EMAIL PROTECTED]) | 2455 E. Speedway, Suite 204 | | (520) 319-7773 | Tucson, Arizona 85719 | *---------------------*-------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
