Skip to content

Commit 152b814

Browse files
authored
add (#4)
* cleaned data * basecamp cleaned data * baseline for gitlab * renamed to gitlab-handbook * added a baseline
1 parent 64a728c commit 152b814

File tree

1,213 files changed

+160288
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,213 files changed

+160288
-0
lines changed
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# 37signals Is You
2+
3+
Everyone working at 37signals represents 37signals. When a customer gets a response from Merissa on support, Merissa is 37signals. When a customer reads a tweet by Eron that our systems are down, Eron is 37signals. In those situations, all the other stuff we do to cultivate our best image is secondary. What’s right in front of someone in a time of need is what they’ll remember.
4+
5+
That’s what we mean when we say marketing is everyone’s responsibility, and that it pays to spend the time to recognize that. This means avoiding the [bullshit of outage language](https://signalvnoise.com/posts/1528-the-bullshit-of-outage-language) and [bending our policies, not just lending your ears](https://signalvnoise.com/posts/3513-when-empathy-becomes-insulting). It means taking the time to get the writing right and consider how you’d feel if you were on the other side of the interaction.
6+
7+
The vast majority of our customers come from word of mouth and much of that word comes from people in our audience. This is an audience we’ve been educating and entertaining for 20 years and counting, and your voice is part of us now, whether you like it or not! Tell us and our audience what you have to say!
8+
9+
This goes for tools and techniques as much as it goes for prose. 37signals not only tries to out-teach the competition, but also out-share and out-collaborate. We’re prolific open source contributors through Ruby on Rails, Trix, Turbolinks, Stimulus, and many other projects. Extracting the common infrastructure that others could use as well is satisfying, important work, and we should continue to do that.
10+
11+
It’s also worth mentioning that joining 37signals can be all-consuming. We’ve seen it happen. You dig 37signals, so you feel pressure to contribute, maybe overwhelmingly so. The people who work here are some of the best and brightest in our industry, so the self-imposed burden to be exceptional is real. But here’s the thing: stop it. Settle in. We’re glad you love this job because we all do too, but at the end of the day it’s a job. Do your best work, collaborate with your team, write, read, learn, and then turn off your computer and play with your dog. We’ll all be better for it.
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
We’re happy for others to use this handbook as inspiration for their own organizations! The structure is fair game to copy. However, please don’t use our words exactly if you are making your own handbook. Personalize to match your own organization, including of course the examples. Thanks!
2+
3+
(And yes, we realize this isn’t an officially recognized open-source license.)
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
[Read on basecamp.com](https://basecamp.com/handbook)
2+
3+
# 37signals Employee Handbook
4+
5+
For over 10 years, we didn’t have a handbook. In those 10 years, when a new person joined the company, they were expected to figure things out for themselves. But when we grew from a company of 10, 20, 30 employees to now a company of over 80, our “introduction by immersion” style stopped working. New hires felt lost and isolated, and their first weeks or even months on the job were stressful because of it. It can be unnerving to join any company, but perhaps 37signals in particular, given how different some of our practices are. There’s as much to unlearn as there is to learn. Prior to this handbook, navigating that path was both somewhat random and almost entirely oral. For a company that prides itself on clarity and writing, that just wasn’t right.
6+
7+
So, this is where we’ll try to share what’s worth knowing about 37signals the company, our culture, our process, and our history. It’s a guide to understanding what people are talking about when they call for “judo” (redefining a hard problem into an easy one) or whether it’s okay to take your vacation when you’ve only been with us for a month (yes).
8+
9+
This handbook also offers us an opportunity to clarify who we actually are as a company. What do we stand for? How should we work? Codifying those beliefs into a handbook makes them tangible and, most importantly, editable. Making the company our best product is a guiding principle, but we can’t easily improve what we haven’t articulated. So whatever version of this handbook you’re reading, you can be sure it’s not the last. Please do help keep it up to date! And by up to date, we’re not just talking about misspellings and team changes. It’s just as much “we say we’re about X, but what we’re really doing is Y”. So many of these employee handbook projects turn out to be ideal-case prescriptions rather than real-world descriptions. They cover all the ways people should act, not the ways they actually do. That’s a sham. Let’s not write a handbook like that. Let’s keep it honest.
10+
11+
If you’re reading this just after joining the company, it’s particularly on you, actually. It’s harder for us slowly-boiled frogs who’ve been with 37signals for a while to spot the broken ways. Please take advantage of that glorious, shiny ignorance of being new, and question things.
12+
13+
## Sections
14+
15+
* [37signals Is You](https://github.com/basecamp/handbook/blob/master/37signals-is-you.md)
16+
* [What We Stand For](https://github.com/basecamp/handbook/blob/master/what-we-stand-for.md)
17+
* [What Influenced Us](https://github.com/basecamp/handbook/blob/master/what-influenced-us.md)
18+
* [Vocabulary](https://github.com/basecamp/handbook/blob/master/vocabulary.md)
19+
* [Product Histories](https://github.com/basecamp/handbook/blob/master/product-histories.md)
20+
* [Where We Work](https://github.com/basecamp/handbook/blob/master/where-we-work.md)
21+
* [Benefits & Perks](https://github.com/basecamp/handbook/blob/master/benefits-and-perks.md)
22+
* [Getting Started](https://github.com/basecamp/handbook/blob/master/getting-started.md)
23+
* [How We Work](https://github.com/basecamp/handbook/blob/master/how-we-work.md)
24+
* [Our Rituals](https://github.com/basecamp/handbook/blob/master/our-rituals.md)
25+
* [Making a Career](https://github.com/basecamp/handbook/blob/master/making-a-career.md)
26+
* [Our Internal Systems](https://github.com/basecamp/handbook/blob/master/our-internal-systems.md)
27+
* [A Note About Moonlighting](https://github.com/basecamp/handbook/blob/master/moonlighting.md)
28+
* [International Travel Guide](https://github.com/basecamp/handbook/blob/master/international-travel-guide.md)
29+
* [FAQ](https://github.com/basecamp/handbook/blob/master/faq.md)

0 commit comments

Comments
 (0)