|Problems? Is your data what you think it is?|
Let's not forget the chainsaw !by ZlR (Chaplain)
|on Mar 31, 2012 at 12:38 UTC||Need Help??|
Note to self : remember to get those xml
I'm not a developer.
I'm always amazed by the level of what you real developers do. Some of the answers I get on this site make absolutely no sense codewise, unless I take 2 hours to decipher them (and I'm not even talking about obfu). Some of the higher layer questions are just way past my understanding of how a language works. It's been like this since forever, I did some coding at the University, but never got to the pro level I guess, and got used to the fact that there are some things I won't take time to understand or learn (also, maybe I'm too slow ;)
So, I'm not a developer, but still, I code a lot.
Most of my projects begin with auditing a client's infrastructure. Sources describing the existing systems can range from system commands outputs to tivoli generated reports, sometimes I get to run the commands I want, sometimes the client gives me a new bunch of zip files every week (things change fast in the real world).
I don't know how other people deal with these kind of projects, although I do see a lot of manually crafted excels with massive vlookups, and these sound both like a lot of wasted work (do it all again in one month) and very much error prone. My Perl scripts are sometimes a little bit quick and dirty but the job gets done. I have enough experience now to be quite confident looking back saying that the result will be error free. And that matters, since in the end this is used to launch system commands on a whole infrastructure.
I also do production Perl, that is Perl automated system actions. We're in 2012, and where I live, Perl is still the only language that's on every Unix system. I understand that development wise competition is fierce, but AFAIC there are no other language used in the system field, except ... Shell.
And that's what I want to say here, with this first Meditation in 7 years or so : Perl is great because it's not only for developers. I have colleagues who were so sick of excel that they turned to doing things in Perl, and it works for them !
Perl is easy and versatile, and not as 'unreadable' as trolls would have it. It's a great tool for productivity, and is still used and needed as the swiss army chainsaw of scripting !
just another Perl hacker,