mbrizic

Each color is a different build running on a different server. And then a load balancer picks which server you'll end up on.

Code-wise, the only difference between the builds is the CSS setting the link color.

I did something very similar a while back: https://mbrizic.com/blog/solarhosting/

There was an interesting article recently about research in bioelectricity, on how each cell is equipped with the same mechanisms of data transfer and storage as a neuron is. Definitely big if true, the implications of that are crazy:

https://www.bitsofwonder.co/p/a-revolution-in-biology

Over the course of my 6 years in software so far, I have written at least that many versions of similar code generators in whichever language we had in the project at the time.

But it's only this time that I decided to build something that's not baked into the system, but rather an external tool that you configure per project how it should be used.

So instead of keeping a "template project" committed in a repo that your generator uses, with this approach you "describe" the templates in a config file, which generator picks up and creates new files based on them, performing all necessary string replacements.

That way it's lot simpler to create and maintain your templates. But honestly, I created the tool as configurable as it is primarily as I want it to be _the last_ generator that I have to write.

And in light of recent NPM drama, the tool has zero dependencies in runtime (although some are used during development, like Typescript or Jest).

I'd appreaciate the feedback about this. Thanks!