The Projects
In total, I completed eight of the projects, and failed to ship anything twice. See below for links to each project, along with my commentary about each of them.
During the month of April 2021, I set out on a challenge. It had been over a year since I last worked on any web development project, and it was clear that I'd fallen out of practice. To get myself up to speed, I challenged myself to design and ship ten different projects in the space of 30 days. To make it more interesting, I set a handful of rules to follow.
Things went off the rails almost immediately.
In total, I completed eight of the projects, and failed to ship anything twice. See below for links to each project, along with my commentary about each of them.
To complete everything in the space of a month, each project will need a three-day turnaround time on average. I could play it safe by reusing technology stacks across projects. But to make things more interesting, I've set a few additional rules for myself.
Don't use a library more than once.
If it's code someone else wrote, I can use it in exactly one project, and nowhere else.
Exception: Top-level dependencies only. I can only intentionally use Lodash once, for instance, but this challenge is demanding enough without forcing myself to audit every other library for it.
Don't use a style more than once.
Each project must have a distinct look and feel, even if they have similar content or functionality. As a rule of thumb, don't use a primary color more than once, and don't reuse common layout patterns.
Don't use a build tool more than once.
Let's make this even harder. Grunt, Gulp, Webpack. Any tool that automates or transpiles code may be used in exactly one project.
Exception: As with the rule about libraries, this applies to top-level tools only - plugins for tools are fair game. Basic usage of npm is also allowed.
