Rocket Insights is now part of Dept Engineering. This project has been moved to deptagency/engineering-soapboxes
This is a collection of preferred practices for web development at Rocket Insights. It comes from our collective experience working on software projects for many, many clients.
Let’s start by talking about what this project is not:
This is not a list of rules you must follow when working on a development project at Rocket.
You're an adult. And we hired you to be part of Rocket because we think you're a good developer.
This is not meant to be an end all be all documentation of everything we do and everything we believe.
The world changes, especially the tech world. More importantly, each client and project has its own subtleties and needs. The chances of even being able to follow one set of rules for any given project is pretty much zero.
So, what is this project for then?
It’s to give Rocket developers a launching off point (see what we did there? 😁).
It’s to give Rocket developers ideas of where to start.
It’s to answer the question: “How do we usually do web development at Rocket?”
It's also to share with clients and prospective developer hires so they can get a flavor of how we do things here.
Finally, it's meant to be flexible as technology changes and our practices change over time. It's a living document, meant to be contributed to by everyone at Rocket. See CONTRIBUTING for details if you see something that's off or that you think needs to be added.