Side projects made me a better software engineer.
I tried to spend a few hours every week working on my side project.
I wasn't trying to build a SaaS and ship to production.
In hindsight, I should've tried (more on that later).
Here's why I found this valuable:
- No technology constraints
- No hard deadlines
- No distractions
It's just me and the application I want to build.
I was free to explore new technologies and figure things out.
When I solve problems myself, I learn the most.
For example, I was stuck for days trying to build a deployment pipeline to Azure.
I couldn't get it to work reliably for some reason.
But I wasn't about to give up.
Another time, I was bent on building a code coverage report.
I learned about coverage tools, report formats, and integrating that with a CI pipeline.
I used Codecov and was pretty happy when I could finally browse code coverage.
Why is all of this important?
The skills you'll learn while solving these problems are transferable to your job and will make you a better engineer. Guaranteed.
Back to the SaaS story.
Building something other people will use is probably the most fun thing you can do as a software engineer.
I'm working on something exciting for the .NET community.
And let me tell you, all those side projects are coming in handy.
P.S. Try out the Vertical Slice Architecture for your next side project: https://t.co/CGG8x1f7JG