Zemanta keeps process, product development and engineering practices transparent, forkable & documented (hopefully open someday).
The goal of maintaining documentation of "how we do stuff" as a repository of markdown files on github is to treat our process:
- transparent - here for everyone to see
- forkable - everybody on our team is empowered and encouraged to improve and refine our process, so just send a pull request, we'll discuss this ASAP within the team and implement the changes
- documented - helps new hires to "get around" faster, makes everyone aware of what the team expects of them
- Services - the purpose of slack, google apps, github, new relic ...
- Team Organization and Structure - how the team functions and operates from a high level perspective ...
- Lifecycle of a Task - the best way to learn about the process of product development and engineering is to follow the life-cycle of an idea, evolving into a product feature all the way up to code running in production
- Code Reviews - team value: no single line of code shouldn't go into production without an additional set of eyes passing through
- Coding Practices - by no means a "set in stone" internal guideline, but a non-exaustive collection of good practices collected over time
- Testing - multiple angles on how to keep your code tested
- Monitoring - making sure we'll be able to monitor your code once on production
- Ecosystem - explained the ecosystem we use at Zemanta
- Helpful Resources - tutorials to help you learn technologies we use at Zemanata, as effectively as possible
If you're a new hire, we recommend reading through these documents very diligently. Asking questions and requiring clarifications is entirely appropriate and will enable us to refine the documentation where it lacks details and clarity. Thank you!