I turned my side-project into a startup. I'm Ido Shamun, AMA!View other answers to this thread
When it comes to architecting large systems, what does one put into perspective before making a decision?
As regards Open Source Contribution, What practical steps can a newbie take in order to get started?
For someone curious about starting their devops engineering journey, what important skill set one must have?
What type of portfolio projects do devops engineers need have to show that are employable and capable?
Hey Nonso Amadi,
Thanks for your questions.
Usually, systems don't start with a large scale. You slowly build them, going step-by-step. It's important to turn big decisions into tiny deployable pieces. Change -> Deploy -> Monitor -> Iterate. If you follow this rule of thumb, it's easy to rollback wrong decisions.
First, focus on open source projects that you use and well familiar with. Second, look for issues labeled with "good first issue". Usually, these issues will help you onboard and learn the codebase.
Be open-minded and constantly learn. DevOps engineers have a great responsibility and in many companies, they're the architecture leaders.
Unlike frontend engineers, DevOps engineers can't proudly show their projects. My advice is to write blogs and contribute to open source projects.