Alright, so today I’m gonna walk you through something I’ve been messing around with: evan shawver’s stuff. I stumbled upon his work a while back, and it really caught my eye, so I decided to dive in and try to replicate some of it.
First off, I started by downloading the necessary software. I needed a specific version of Processing and some libraries he mentioned in his tutorials. That took a bit of digging, but eventually I found the right downloads on some obscure forum. Always a good feeling!
Then came the real challenge: understanding the code. Evan’s code is pretty clean, but it can still be a bit dense if you’re not used to that style of creative coding. I spent a good chunk of time just reading through the code, trying to figure out what each line was doing. I even printed out some snippets and annotated them with my own notes.
Next, I tried to run some of his examples. And guess what? They didn’t work right away! Of course not. There were always some dependencies I missed or some settings that needed tweaking. I spent a couple of hours just debugging, reading error messages, and Googling like crazy. Eventually, I managed to get a few examples up and running.
After that, I started to experiment. I took one of Evan’s basic sketches and began to modify it. I changed some colors, added some noise, and played around with the parameters. It was really cool to see how small changes could have such a big impact on the overall visual effect. I kept tweaking and iterating until I had something that I was really happy with.
Here’s a little breakdown of what I learned:
- Don’t be afraid to get your hands dirty. Just jump in and start experimenting.
- Read the documentation. Seriously, it can save you a lot of time.
- Debug, debug, debug. Expect things to go wrong, and learn how to fix them.
- Don’t be afraid to ask for help. The creative coding community is really supportive.
And finally, I documented everything. I wrote down my process, saved my code, and took screenshots of my results. This is super important if you want to be able to recreate your work later on, or if you want to share it with others.
So yeah, that’s pretty much it. Messing with Evan Shawver’s work was a really fun and rewarding experience. I learned a lot about creative coding, and I’m excited to continue exploring this world. Now I’m going to try something else, maybe with * or something. We will see.
Anyway, that’s how I went about tackling Evan Shawver’s stuff. Hope it was helpful! Catch ya later!
