between workforpie and path.to [0] shutting down within 2 weeks of eachother, there is something to be said about new attempts to try to crack the old recruiting regime turning out to be more difficult than one might think.

[0] http://blog.path.to/post/six-lessons-that-might-have-saved-o...

Let me know if you're ever in utah and want to play a round.

Sure thing, thought I haven't had a reason to go to Utah before, but you never know

I think this is a good reason: http://www.utah.com/nationalparks/bryce.htm I've been there two years ago during my honeymoon and I found it beautiful (probably the best park I visited - together with Yosemite - in my west coast fly & drive tour)

I'm building a platform to enable just that for businesses. It's mostly geared towards marketing integration and automation but could really be used any way imaginable.

Having used Dericks (the OP) Marionette package and interacted a few times with him, I can attest he practices what he preaches.

Looks great - except missing the one I need for my product: LinkedIn! any timeframe for linkedin?

great follow up to first discussion: http://news.ycombinator.com/item?id=4555165

I really enjoyed this list. Having similar experiences is exactly what led me to do something about it and build a new approach to recruiting which we are in pre-launch mode: http://betacave.com

Here is how our platform addresses each of your concerns:

1. Phone calls are the 2nd step and not the 1st

All personal information is private. On betacave, recruiters can't get access to you unless you specifically allow it. I'm now telling recruiters that call me that if they want to connect, they'll have to go through betacave.

2. Read my CV

We will provide tools to hopefully enable recruiters (both 3rd party and companies) to see how a candidate who has expressed interest matches with what they are looking for. Although we hope to make easier, it is still up to recruiter to actually care and read about you.

3. Know what you are doing

Same as #2, we hope to make that easier for recruiter to know about you (if you want them to).

4. Don’t ask me to fool my customer

Not much we can help with that. That's just common sense.

5. Respect my requirements

Exactly! Our learning algorithm will learn about what your requirements are based on your input and some machine learning to only send you matches that fit your requirements.

I'd appreciate you check out betacave.com and let me know if you think it would help reduce the friction involved with dealing with recruiters.

Any pointers on how to make it easier to wtfm? If anyone out there actually enjoys writing documentation I'd be willing to pay for some help and guidance on a rather large commercial open source project that is in need of some tlc regarding documentation

In the Python world, readthedocs.org has made writing docs easier - it takes care of rebuilding documentation each time you commit. It's implemented in Python, and most popular with the Python community, but it can be used for other languages as well.

Sphinx is pretty nice, even if it is not a python project.

http://sphinx.pocoo.org/

API documentation can be generated from the source code with tools like doxygen. For everything else there's the standard toolchain consisting of a good editor and source control. Writing documentation is a chore but it's a very important aspect nevertheless.

I'm a marketing and technical writer - take a look at the URL in my profile and get in touch if you are interested.

I have thought alot about this lately (having just started a company that I believe addresses this: http://news.ycombinator.com/item?id=4576038 ).

for me there was just too much friction in the process which is what we think our model can remove/reduce.