grease

tldr: In the 1950's, doughnut shops were some of the first food businesses commonly open late at night. They became hot spots for police working the night shift since it gave them a place to grab a snack, fill out paper work, or even just take a break.

Fair point, thanks. Changed the title to be more accurate.

Rich made some interesting points on developing libraries in such a manner that it doesn't introduce breaking changes (for the calling code). Does anyone here agree (or have counterpoints) to his suggested approach?

All your points (1 through 4) matched with what was looking for. I chose Clojure. It's Lispy, focuses on immutable data (but not necessarily pure functions), has a version (cljs) that compiles to javascript (if you're writing web-apps, its great to write both your front-end and backend code in one langauage). I've broadly found clojure to be a "practical" functional language to work in.

(If it helps, I'm primarily a python/js developer before picking Clojure).

Yes, and here's why.

A team's picture gets better when it sees collective participation from a large number of people in the team. Which is why I feel this will beat company LI/FB pages, that are updated by a single person(or a select few)

Got it. Agreed.

Good point.

In (email) targeted recruiting, the recipient will check the company out first. Isn't it worthwhile to build what they would like to see?

IMO Glassdoor reviews suffer from extremity bias. For some reason, most reviews there either sound artificial or angry.

More importantly, glassdoor gathers "what people think of a company". Isn't it more interesting to know "how people think in a company"?

Yep, starters on me. Or recruiterbox, to be more precise :)

Look forward.

If you guys are ok, I don't mind sponsoring pizza for the meet. Let me know.

I'll try to make it

@Jonovono How do you ensure that your search is constrained over music videos only?

Does the Mandrill inbound email system parse out quoted text?

I am curious to know if more companies have seen success with "the Sunday test" type of hiring philosophy that Greg talks about

Linkedin public profile URLs are notoriously clumsy to remember and share. I am curious how many people signed up for this.

I think the OP's argument is that a lot of reactive feature-building (irrespective of how they are organized) is a bad idea - especially in the early stages of a product.

1) Its hard to say anything conclusively from a conversion perspective yet. 2) A lot of visitors go to the tour before signing up. That is also where they spend most time. 3) Not really. Most pages are still in a transition, and we're trying a bunch of things. Currently, the changes are based on "what we want our users to know", rather than user feedback

The current payment system is in transition - we want to eventually move to the recurring payment model like you mentioned. The reason it stands today is that things like managing change of plans, trial periods etc is a big pain with paypal. We're exploring various (non-paypal) alternatives to this.

Hi. I'm one of the creators of Recruiterbox, and pleasantly surprised to see that someone has posted about us us here. Will try my best to answer any questions/comments

Its a good thought, but right now, we're more focused on helping companies just organize their existing way of hiring (and not change their ways themselves)

We're working on a live demo.

I totally relate to this. Most recruitment tools are cumbersome and a job in themselves. We wanted to build something that gets out of your way and gets the job done.

We are django app - do you know Liquid like frameworks for django? Suggestions welcome.

Good points ... we are trying out a few combinations with the layout - hopefully, we can make it easier for people to do both: find what the app does and register

Yeah, we do ... In fact they were our first clients

Yes. Subscriptions can be paused/cancelled any time.

Thanks, yeah will do this :)