Last active
August 29, 2015 14:21
-
-
Save yejianye/5f341323af857b97e22f to your computer and use it in GitHub Desktop.
Engieer Culture at Glow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Engineer Culture at Glow | |
--- | |
## Should we really care about culture at startups? | |
Good culture makes a company more efficient and scalable | |
- Lower communication cost | |
- Helps individual development, especially for junior members | |
- Makes the team unique | |
- Essential for building a long-lasting company | |
--- | |
## Examples of successful team culture | |
Facebook - Move fast and break things | |
Github - Asnychronous communication | |
Instagram - Optimize for minimal operational burden | |
--- | |
## Team culture at Glow | |
- Our CEO Mike defined 10 core values of Glow in early days of the compnay | |
- Show commitment in everything you do | |
- Hard work pays | |
- Got to have fun | |
- ... | |
--- | |
## Engineer culture - Software design | |
- Capture every piece of data and make it highly avaiable | |
- Simplicity over extensibility | |
- Embrace cloud-services & open sources projects | |
--- | |
## Engineer culture - People | |
- You own product features not code modules | |
- Make your work visible so that others | |
- Know your progress, potential risk | |
- Be able to review and audit your work | |
- When encountering issues, offer solutions not excuses | |
--- | |
## Engineering Tasks & Refactors | |
Priorities: | |
1. Cut down development time | |
2. Improve data integrity | |
3. Improve app performance (client > server) | |
--- | |
## Post-mortem | |
You should always do post-mortem for every major incidents | |
- Write it down | |
- Focus on reducing system-error instead of human-error | |
--- | |
## Learn & Share | |
- If you're too busy with work and don't have time to learn new things, it's bad for you and for the company. | |
- To maximize the value of your learning is to share with the team, or with all developers in the world | |
- Internal tech talk | |
- Tech blog, http://tech.glowing.com | |
- Open source project, http://github.com/Glow-Inc | |
--- | |
# Q & A | |
--- | |
## Thanks! | |
### We're hiring! | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment