The beginning

Imho, one of the best things you can do to learn to code is to work on a project. Unfortunately, once of the hardest things to do when coding is to pick a project and then stick with it.

Early in 2019 I decided on a project and have been working on it ever since. I’d had many projects before that were one offs but none really got past the planning stage. This one required everything, a mobile app interacting with webapis and multiple types of data storage with a portable architecture that was cloud provider agnostic.

Fast forward to 2020 and the application is moving along, still in alpha as I add more features and address kinks and gotchyas in my designs. A few months ago, I brainstormed a feature and went to go inspect the affected code and, to my surprise, realized I had already implemented this work and had just forgotten it was a thing. Additionally, this project has been a great way to tackle problems that don’t get prioritized at my full time job and prove out solutions since the tech stacks are similar. There have been a lot of learnings and gotchyas since I started down this path and it had become obvious that my current method of star and flag messages with docker run commands and textfiles with k8s configs named scribbz.txt did not scale… at all.

So, here we are, another excuse to use k8s I’ve deployed a wordpress site with one of bitnami’s helm scripts, Edit: WordPress behind a reverse proxy is a pain . Edit 2: Haha, wp behind a reverse proxy is dumb and solved! However, this did provide it’s own learning and gotchyas… in a meta sort of way. I intend to use this as a new singular place to display my learnings as a record of how far I’ve come and to help any poor souls that wander by.

Thank you for reading.

Leave a Reply

Your email address will not be published. Required fields are marked *