| I think breaking a bit from the current de-facto format would be better. Consider the example: == Acme Products | Test Engineer | Las Vegas, NV; Austin, TX | Onsite; Remote | Full-Time; Part-Time | Visa (H1B) | Tunnel Theory; Kinematics Engineer needed to test prototype products. Must be able to lift and carry anvils.
metafriendly == The only real problem I've had with existing listings, is that people tend to list both "remote" and "no-remote" -- making search hard. I propose moving those "tags" to "hash-tags", and just list them at the bottom of the ad: == Acme Products | Test Engineer | Las Vegas, NV; Austin, TX Engineer needed to test prototype products. Must be able to lift and carry anvils.
metafriendly #on-site #full-time #part-Time == Note that the two are different; I don't see how you could work remotely testing anvil-lifting... ;-) At any rate, if we're talking about a new "spec", I'd say: * Apart from position, and location, as little as possible on the first line. * Replace the "text"-tags with "hash"-tags - #remote is easy to search for with text-search, and won't match #no-remote, No-remote -- and doesn't require regexp magic to match word-boundaries etc (which few (no?) browsers support anyway). * Put the tags at the bottom -- they're really for searching (and machine parsing), with the amount of listings we are getting now -- no-one is reading just your ad, they're reading a stream of ads. * Don't go overboard with "hash"-tags. I'm not all that interested in seeing: mulitple-line lists of #python #ruby #haskell #c++ #dev-ops (...) Now, if we really want to over-engineer this thing, why not draw some inspiration from the Dewy decimal system? So 001-234 could be 001:devops 2:python and bash 3:unix-like-and-windows-nt 4:remote-or-onsite ... ;-) |