3 ms·
Very cool. I really like the command line interface. I've been dealing with a lot of recruiters over the past year. I even wrote my own Rails app: https://gith
by klenwell 11y ago
Very cool. I really like the command line interface.
I've been dealing with a lot of recruiters over the past year. I even wrote my own Rails app: https://github.com/klenwell/recruiters-on-rails https://github.com/klenwell/recruiters-on-rails.
I have found it pretty useful in tracking the ones I deal with more substantively but one use case I have had trouble dealing with is in initial encounters and deciding whether it is even worth the effort of adding a new recruiter to my app. I get enough recruiter spam that the cost of simply filling in the form on my app to add each recruiter could be prohibitive. Nevertheless, I'd like to keep a record with any recruiter I deal with, even if it is just spam or template email.
I currently have a de-facto solution that involves the autocomplete feature in Gmail search and Mailchimp mailing lists. But I can see this solving this problem much more neatly and coherently. And as a Ruby gem, I could imagine even integrating it with my Rails app.
Great work!
- jacobevelyn 11y agoThanks! I'd love to hear how well/poorly this integrates with your (very cool) app. Do feel free to create GitHub Issues if there are things you think should be changed to allow easier interoperability. In particular I'd love to hear how this works as a standalone Ruby library (the `Introvert` class should help you more directly than the shell commands), since I tried to separate the internals from the command-line interface (which is in bin/friends) but I think that separation is somewhat blurred at the moment.