The whole point of this story is: I got a callback on that web app developer position at Buff State
. Seems I didn't completely fuck up my chances of being hired yet and, despite not having exactly the experience they're looking for [cf: Appendix I] it seems they still want me to have a short 3-hour chat with the search committee, the web team, and the web administration director. Privately I am shitting minibricks because the main reason I applied for the job was because it would be idiotic not to [double my salary, plus benefits, government job, &c.]. I was not really looking for a job. It's more like Laff in the Dark. I'm just cruising along in my uncomfortable little car with, like, bats in my face or something, and then it's like BAM! motherfucker! send us your resume. And then I fall right off the end of the extended metaphor into some kind of Search Committee asking me for references.Which brings me to another, premature point- anyone want to be a web applications developer here? It involves Macs and Adobe Creative Suite and dealing with weirdoes and PostgreSQL and Zope ... lots and lots of Zope.
Also I saw (e:enknot) and (e:paul) at Cafe 59 at lunch today. We discussed the merits of a column in my paper about extremely dorky things that nobody would ever understand. We think it's a great idea, but I'm not convinced that the public is Ready for that kind of nerdiness.
- Z
_______________
Appendix I: They are seeking a web applications developer with custom CMS development experience [this is something I have been doing for several years]. They also want a few years of PHP and Oracle experience. I've used PHP extensively and I was allowed to fiddle with Oracle a little at school, but I have almost nothing to show for either. I've always been of the opinion that the stuff you do is what's important and the language you use is kind of an implementation detail. Employers rarely share this opinion.
Welcome to the club, Jason. Now you understand the source of my frustration in job hunts (your advice comment on my post was very good, though).
There's never any discussion about the stuff that really matters for real programming jobs. Like how well you document your code, learn a new technology, create reusable code, use existing documentation, work with other programmers, use a source versioning system, design solutions that allow for future flexibility, etc. Hell, in my experience negotiating the politics of what end users want/need vs. what their managers want/need by itself takes up more time than actual coding.
While I wouldn't expect a technical recruiter to know how to program in a specific language, I would expect someone whose job it is to recruit such people to have some common sense to look for the kind of stuff that's in the above paragraph.
"Employers rarely share this opinion."
Noooo shit man. Hell, I was told this week....hold on a tick, I wasn't told this straight up, but it was incinuated that if you don't use X language in Y amount of time then you must not know X! Very very very stupid, an opinion of someone who obviously never wrote one goddamn line of code.
Anyway I think you should do what's best for Zobar, and if that means moving on then why not? I know you'll make the right choice.