[saosebastiao]

Is anybody else surprised that a 20 person company has the resources and prioritization to create something like this?

[znq]

If profit is not the priority, there's a lot of things a company can do. To be honest, from our own experience of scaling up the company, the years between 0-10 employees were the most difficult ones. Now, 7 years later running an established company with a great reputation and 20 excellent team members leaves a lot of room for experiments and doing things like this.

[sonofgod]

Cynically, it's a recruitment expense -- there's a pretty good probability of getting a good hire from posting this widely.

It's not, to my mind, an actual corporate handbook -- it's missing boring important things like "here's our password and security policy, please remember we have people's super-personal health data in our apps, so it's really important". I guess that's probably in the company Wiki or similar.

[znq]

To be honest, we're currently not really thinking of growing the company much. But you're right.

However, this whole thing started out as a Onboarding Handbook for new team members. Then however we thought it's also a great book to share with the world. So we decided to remove certain items and have those in the internal wiki only.

[wushupork]

I own a small dev shop and I thought this was a great idea for recruiting. No need for cynicism.

[totalrobe]

This is a great tool, inspired I'm sure by the transparency of others like 37signals. It is not a "company handbook", it's:

1) A recruitment tool

2) Marketing

[jgimenez]

Definitely 37signals inspired us in many of the things we do. I'd say half of our team have read their books and regularly read their blog!

Recruitment and marketing are definitely a good side effect, but as @znq mentioned earlier, we built the guide in the first place for onboarding our own team members, then we thought sharing it publicly would benefit the community.

[louisswiss]

I'm not, no.

[deanalevitt]

Me neither.