Marking #micheledoesweb as done
A little over a year ago I started on a personal project to re-familiarize myself with web technologies called #micheledoesweb. I decided to write a backend for an app I’d built during a hackathon using new to me technologies. I blogged about my progress for about a month, then as usual life took over and the blog posts and work stopped. This is the conclusion post to that project and the last in the #micheledoesweb series.
Over the course of the past year I’ve actually done a lot related to #micheledoesweb. I investigated using different languages and frameworks. I played with AWS and web deployment pipelines. I wrote some code, but not a lot of it. I even migrated this blog from a CMS to a static site hosted on s3 (admittedly that was motivated mostly by grumpiness). With #micheledoesweb I set out some concrete goals for myself around creating a shippable product. In the end, this project barely got past the Hello World phase. When compared to my concrete goals this project was a complete failure. However, I consider this project a success. Why? This March I transitioned to a backend role at work.
The biggest lesson that’s come from this is: when it comes to my goals, I’m the only one who gets to decide if I’ve succeeded. My motivation for starting the project was to learn, and that’s exactly what I did. #micheledoesweb was a success.
This post took 2 hours to write and edit.