In addition to code, you could define exercises around the supporting tasks to take a project from source code to production. Some examples:
Setting up your project on Day 1 on Github. Configuring tools, PR Templates, protected branches, squash on merge, and CI workflows are a great piece to scaffold in the beginning
Dedicate one day to configuring cloud resources for your application
Create a CI/CD workflow where changes that are merged into master are deployed to a develop environment
Creating an automated workflow that builds your code
Creating a CI/CD workflow that deploys your application to production when a release is created
Add a CI step which lints every commit you push to Github
Some other general exercises that would be useful building a career in coding:
Localizing your application so it can be translated
A 'driven' software engineer with a passion for cars and tabletop games. Get it, driven? Because cars and... Okay, I'll stick to writing code instead of puns. 🏁
Perfect list. Sometimes we get wrapped up in the project-specific features as checkpoints for progress (who doesn't want to show off a cool new thing their project does?) and overlook the workflow side of things.
In addition to code, you could define exercises around the supporting tasks to take a project from source code to production. Some examples:
Some other general exercises that would be useful building a career in coding:
Perfect list. Sometimes we get wrapped up in the project-specific features as checkpoints for progress (who doesn't want to show off a cool new thing their project does?) and overlook the workflow side of things.
What a wonderful idea to add to the list! I will definitely add more behind the scene type tasks. Thank you for your suggestion