Dev Rando Challenge
Goal
Build something with what's given to you, no compromises.
"What I like about this is that it's basically forcing JS devs to make something without deps, but they still get to have deps, and they still get to peer inside node_modules once in a while and see fifty billion files."
- Benton Boychuk-Chorney
Inspiration
Dev Rando draws its inspiration from the exciting world of game randomizers, particularly those created for classics like The Legend of Zelda: Ocarina of Time. See: Ocarina of Time Randomizer
These kinds of randomizers breathe new life into familiar games by shuffling item locations and altering progression, creating unique challenges with each playthrough. Routes are changed, mental models are broken, old gives way to new, and at the end of the day, you're left with a new appreciation for the original game.
Thus the thought emerged: why not apply this concept to the realm of coding? There's routing of new and unexpected dependencies involved, and you'll need to think creatively to create something that not only works, but effectively leverages whatever dependencies you've got.
These are not the packages you want.
For this first version, we've enforced minimums to prevent proverbial soft-locks (namely, esbuild ). Oh, did we mention versions are random too?
On a more personal note, this particular concept was created by someone who 1. disdains the idea of leetcode and 2. asserts that challenge and project-based code (imo) are far better for people who like to tell stories around their progression. Somewhere out there, there is a cursed Guay Hover of code in TS/JS/NPM which has yet to be discovered by either humans or AI.
This challenge currently shuffles automatically once per month via GitHub Action. Later (early Octoberish), this page will automatically pull and feature public projects published under this autogen package.
This is the one serious section here: no warranty, no guarantees are made as to the functionality or interoperability of the dependencies in the challenge. You should not use the challenge dependencies in a production environment.
This is the first iteration of Dev Rando; please report issues and suggest improvements here: https://github.com/dev-rando/dev-rando/issues. If you have ideas, please share!
"A guy who came to Fight Club for the first time, his ass was a wad of cookie dough. After a few weeks, he was carved out of wood."