Looking for that perfect project for developing new skills. Want to move beyond the tutorial? Well look no further, I’m introducing a year long coding project to give you something fun to play with.
In this exciting project, we’re coming together to craft a team holiday recipe book application. Each month, you’ll receive a new set of requirements for this side project, carefully designed to be built upon but not to disrupt our primary work responsibilities. I’ll also be posting some code in my Github if you want to follow along.
Team building comes in many flavors, and for this endeavor, you can choose to embark on it solo or gather a team. Collaborators from diverse departments, such as design or product, are more than welcome to contribute.
For those opting for the solo route, I’ll guide you through the evolving requirements, providing basic design screens to keep you on track.
Requirements:
- User Functionality:
- Sign-up feature for users.
- Ability to create a recipe
- Admin Features:
- View of people and recipes
- Other
- Additional Considerations:
- Version Control
- Integrated testing
- Production Deployment (AWS, heroku, self hosted)
- Security measures for user data.
By diligently following this schedule, we aim to have our team holiday recipe book ready for launch by November, just in time for everyone to contribute their favorite recipes for the festive season! Let the coding festivities begin!
January: Project Kickoff
Use this month to get yourself setup for success. Understanding how and where this code will live is part of the fun. Are you learning a new language? You’ll need to store users and recipes. Will you use SQL or NoSQL DB for this project? I’ll be posting requirements here as well as the Github project.
- Determine language
- Determine db
- Determine production deployment method
- Determine version control mechanism
- Determine testing method
I’m going to be playing with Ruby on Rails for this. I’ve been walking through some tutorials and plan to expand my knowledge that way. I’ll be using a SQL DB because I like them but I might switch to NoSQL later.