План заняття

І Організаційний момент. Привітання

II. Перевірка домашнього завдання.

ІІІ. Основна частина.

AngelList “corporate policy” is that team members should ask forgiveness, not permission.

We would rather have someone do something wrong than ask permission to do it.

Or better, we would rather have someone do something right and not need permission to do it. This is the most common outcome.

We would rather have people ship to production whenever they want, than go through an internal review process. We can fix it on production. We prefer the customer’s review process. And it isn’t too hard to reveal a new feature to a small portion of our users and iterate on it as we expand it to more users.

Eliminating permission increases speed and diversity

Eliminating permission increases the speed and diversity of our decision-making. Our incubator applications are a good example of diverse decision-making: one of our team members built it even though I was telling him, “This is fine, but I don’t think it is that important. Why don’t you work on something else.” It ended up being very important to our users and mission.

There are some sensitive parts of our product that are walled off from this “ask forgiveness” policy. There are some things we want reviewed by the people who “know better”. But it’s really rare.

How it works

This policy only works if you hire insanely smart and capable people, and let go of the ones who are not. We also filter for people who are mission-oriented, care about our customer and want to learn more.

And it doesn’t mean that the founders aren’t standing over your desk telling you, “this isn’t good enough to ship”. That’s why we write down and promote these ideas. Because there is always pressure from someone important to do it another way.

It also wouldn’t work without these other items of corporate propaganda:

You break it, you bought it

If you break something or your stuff is buggy, please fix it. As in straight away mate.

Sweat the details and corner cases

If people are going to ship whatever they want, we need them to sweat the details if they’re going to avoid mistakes.

The best way to do that is to have the rest of the team constantly complain that your code and/or design sucks or, in polite terms, “contains opportunities for improvement.”

Actually, mistakes are fine. They’re something you trade off for other variables like speed of iteration. We just want people to sweat the details because we care about the details.

Be real

Again, if people are going to ship whatever they want, whenever they want, how do we get them to make good decisions? One answer is that we ask them to “be real”. As in, treat our users like real people. Treat your teammates like real people. Just be real and do the right thing.

Do what you think is right (and be right)

If you have the freedom to make decisions, you also have the responsibility of being correct.

S/he who codes, rules

Another way we promote good decisions is by pushing the decisions down to the people doing the work. We memorialize that with the motto, “s/he who codes, rules”. As in, when we disagree, the person doing the work makes the decision.

Own the result

Pushing the decision-making down to the worker works best if the same person is responsible for the metrics. So we try to have 1-wo/man teams whenever we can, and we ask them to own the result. We also hire people who care about our customer and want to solve problems for them.

Freedom and Responsibility

All of these dictums are variations on freedom and responsibility. Netflix has a great presentation on the topic. So does Valve. Peter Drucker probably wrote about it 50 years ago. We didn’t invent this stuff, we don’t claim to know what we’re doing, nor is this a perfectly accurate or complete model of how we operate.

Freedom

Ask forgiveness, not permission

Do what you think is right (and be right)

S/he who codes, rules

Responsibility

You break it, you bought it

Sweat the details and corner cases

Be real

Own the result

EXERCISE 1 Turn the following into the Passive Voice

1. We received this letter after his departure. 2. Have dogs ever attacked you? 3. Bees gather honey from flowers. 4. The storm drove the ship against a rock. 5. Who discovered the circulation of blood? 6. They are selling delicious fruit ice cream there now. 7. The old man showed us the way out of the wood. 8. They offered her some interesting work. 9. The doctor prescribed her new medicine. 10. They often speak about him. 11. Everybody laughed at this funny animal. 12. We have been looking for you the whole morning. 13. We shall insist on strict discipline. 14. They teach three foreign languages at this school.

EXERCISE 2 Turn the following into the Active Voice

1. The light has not yet been turned off. 2. The boy was punished for misbehaving. 3. By three o'clock everything had been prepared. 4. The dictation was written without mistakes. 5. Whom was the poem written by? 6. Her dress was washed and ironed. 7. I was not blamed for the mistakes. 8. The papers had been looked through and corrected by the next lesson. 9. This house was built last year. 10. The letter has just been sent. 11. This article will be translated at the lesson on Tuesday. 12. When will this book be returned to the library? 13. The room was cleaned and aired. 14. Have all these books been read? 15. Whom were these letters written by? 16. The letter has just been typed. 17. She showed me the picture which had been painted by her husband. 18. I shall not be allowed to go there. 19. He has been told everything, so he knows what to do now. 20. All the questions must be answered. 21. The door has been left open. 22. Betty was met at the station. 23. The girl was not allowed to go to the concert.

24. She said that the new time-table had not yet been hung up on the notice-board. 25. The chicken was eaten with appetite. 26. It was so dark, that the houses could not be seen.

EXERCISE 3.Open the brackets using the verbs in the Passive Voice.

1. I am sure I (to ask) at the lesson tomorrow. 2. They told me that the new student (to speak) much about. 3. The hostess said that one more guest (to expect). 4. The newspaper said that an interesting exhibition (to open) in the Hermitage the next week. 5. This new dictionary (to sell) everywhere now. 6. All the texts (to look) through yesterday and not a single mistake (to find). 7. Two reports on Hemingway's stories (to make) in our group last month. Both of them were very interesting. 8. He said that Grandmother's letter (to receive) the day before. 9. Two new engineers just (to introduce) to the head of the department. 10. Don't worry, everything will be all right: the children (to take) to the theatre by the teacher and they (to bring) back to school in the evening.

Домашнє завдання : переказувати текст

Заняття № 21