Passionate Developer! Loves games, Elixir, and cats.
Who is This?
- Level3 Games (1)
- Careem (+2k)
- 96problems (3)
- Telly (11)
- Sourcebits (21)
Software engineer - IC Track
More Smart People
Subject: Communication Within Tesla
There are two schools of thought about how information should flow within companies. By far the most common way is chain of command [...]. The problem with this approach is that, while it serves to enhance the power of the manager, it fails to serve the company.
Instead of a problem getting solved quickly, where a person in one dept talks to a person in another dept and makes the right thing happen, people are forced to talk to their manager [...]. This is incredibly dumb.
Anyone at Tesla can and should email/talk to anyone else according to what they think is the fastest way to solve a problem for the benefit of the whole company. [...]
One final point is that managers should work hard to ensure that they are not creating silos within the company that create an us vs. them mentality or impede communication in any way. [...]
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Startup Flow Diagram
- Upstream prerequisites
- Maintenance & Evolution
- Identify a problem
- Build focus groups
(Design - Tech)
- Automate from the start
- Else, get dedicated QA
- Never forget: 80 / 20 rule
The Technical Half
- Your first hire will push the domino
- Focus on managerial / process skill
- Developer != Designer
a Tech Team
- Replace "deadline" with "challenge"
- Replace "penalty" with "reward"
- Replace "formal" with "fun"
Mobile Apps as a Use Case
Things Gone South