Skip to content
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
/ guidelines Public archive

Our guidelines and best practices for development and everything around it.

License

Notifications You must be signed in to change notification settings

grrr-amsterdam/guidelines

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GRRR development guidelines

Our guidelines and best practices for development and everything around it.

❗️❗️ Sorry! We moved everything to Coda, our new internal documentation tool. This repository is archived.
Please find the Development Docs here.

Mantras

  • We start developing when there is a clear scope.
  • We strive for test-driven development.
  • We work in small, feature-based iterations.
  • We code to the best of our abilities, according to our coding standards.
  • We version our files with Git.
  • We use Docker for parity and to be up and running in no time.
  • We deploy our work to publish it to the world.
  • We set up our servers to run as smoothly as possible.
  • We monitor our work to make sure everything keeps running.
  • We share knowledge with the community on our blog.

Contributing

Please use relative links when referring to other documents in these repository.

– GRRR

About

Our guidelines and best practices for development and everything around it.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published