never seen that in a job posting before...

[cellio]

From this job posting for an API Technical Writer (sic):

"Our ideal candidate [...] Comfortable authoring in HTML and XML using plain-text editors (no WYSIWYG)"

That's how I work all the time. I didn't know anybody else cared. :-)

(Because (1) after 30+ years the emacs muscle-memory is strong; (2) it means I actually know the spec (at least the important parts); (3) I don't have to clean up after tools' bad decisions about what I meant.)

Comments

[cellio]

True, true, and I'm well aware that the right tools make a huge difference. Currently we are lobbying to upgrade to a modern version of IntelliJ when the standard corporate answer is Eclipse, because it really is that much better for us. It's an uphill battle, but we're getting some traction.

The "no script kiddies" approach would be much better, but I imagine what happens when they try that is that HR (allergic to bluntness like that) turns it into "must know HTML" and then gets bunches of people who think that means "can make HTML come out", and the developers have to weed them out.

[metahacker.livejournal.com]

Yeah. :-/ The game of telephone works both ways.

Yay, IntelliJ. Uphill battle at my workplace, too...

[http://users.livejournal.com/merle_/]

Heh. I'm in a place trying to standardize on Eclipse over IntelliJ. Wonder if this will be the future emacs/vi schism. (yeah, I'm vi all over ;-))

HR needs developers to vet job postings. Support needs developers to determine root causes. IT needs.. yeah. My career as a developer has been stunted because I want to help these people (and do so), which means I get less actual coding done, and the positive effect for the company is hidden from my bosses. Eh.

Have keyboard, will not travel.