I used pico. Until the day that I opened a file larger than my combined swap and memory… and linux started shutting processes down. I then resolved to learn more vi commands, which was the only reason I used pico in the first place Ignorance.
Linux (mostly slackware) geek, tooled about with Solaris and Irix, worked on … ohgoditsbeenawhile… unix emulated system on ibm’s os390 - a mainframe OS. Weird weird stuff. Been meaning to install a BSD os for a while - waiting for hubby to clear off his laptop so I can. Writing PHP, I have written bash (I ran into a LOT of bloat writing a bash/dialog script to customize ipfw way back when that was current, and then learned perl) some javascript, html of course, asp, SQL, yadda yadda.
Always wanting to learn more, but I’ve been stuck with support jobs that have me working more in MS OSes than I like. And now I’m a waitress - well, maybe I can take up geeking on my spare time.
I’ve been a pro geek since 1985, hacking COBOL on IBM MVS System 360. Started doing DB2 in the version 2 era. I was so used to the ISPF editor that I bought a Windoze version when I started working on that platform. I’ve had formal training in Fortran, PL/I, COBOL, and assembler (both 8080 and System 360). I’ve taught myself C, C++, Java, and a bit of Perl and Python. I still have a deck of punch cards laying around the house somewhere. As an exercise, we wrote a simple ‘hello world’ type assembler program, hand translated it into machine code, and entered it into the system by setting the switches on the front of the Altair 8080.
These days I split my time between Windoze and *nix, mainly Linux and Solaris. If I need to do some quick lite editing I’ll use vi (even on Win2K thanks to RKTools) but for heavy coding I use the excellent JEdit.
Hardware geek checking in. I design chips. Which mostly amounts to years of boring Word documents, punctuated by a few blissful months of VHDL writing and simulation on a SunOS box.
Religious afilitions: bash, vi (better yet, vim), perl and pine
just wanted to through in a plug for vim for all you vi heads. It’s all the fun and power of vi, with the only the good bloat from emacs. Multiple buffer frames, multilevel undo, syntax highlighting, visual selection… shweet… (And no bloody tetris or chat).
The other day, I was trying to explain the beauty of vi to my fiancee, a devoted pico-ist. I started with simple regexp stuff that (to my knowledge) pico can’t do and worked up. (yeah, I know, that’s technically ex, not vi I was showing off). I got up to something like
when she finally broke and said: “That’s just ludicrous. LOOK at it. Don’t you see? It’s gibberish!”
Pro geek with a Comp Sci degree. I understood the subject line almost immediately. That’s in spite of the fact that I’ve done almost no *nix work in recent years. I occasionally telnet or ftp from Windows to a Unix shell and do some simple things like navigating and listing directories or transferring files. 5 or 6 years ago I was doing some pretty heavy Perl stuff under Unix. I miss it.
Look here, I’m a QA/CM specialist. I don’t care what you guys do as long as it is version controlled in a suitable repository, has been appropriately tested and approved by the users.
… you want me to compile what? have it to the users by when…?
…and meanwhile, you have me: GOAT (geek of all trades: master of none), who uses whatever gets the job done.
Wish I had more time to play about with *nix systems, however. Need to get back up to speed on 'em, but like davidm, I understood the subject line pretty quickly.
What, no test scripts in a closed loop test lab Opengrave?
'nother geek here too. Although not actively programming anymore, I did a lot of PL/SQL in Oracle, on UNIX. I usually used telnet session(s) against piped into an HP box with UNIX v11.x. I used VI all the time, hands down. I love it. In the office we use Linux. The powers-that-be feel that Linux is more virile than eunuchs. Okay, cheaper at least.
I did have OpenBSD on one of my boxes at home for months, but I eventually scrapped it and went back to Linux. OpenBSD kicked ass, no doubt about it, but Linux could easily support some routing trickery that OpenBSD couldn’t, at least not at the pf/ipf level.
Ignorance.
I occasionally telnet or ftp from Windows to a Unix shell and do some simple things like navigating and listing directories or transferring files. 5 or 6 years ago I was doing some pretty heavy Perl stuff under Unix. I miss it.