👩💻 I've started #100DaysOfCode on October 23rd and have been getting more shit done ever since (speaking in terms of personal projects and learning stuff). I haven't been able to commit to it on a day to day basis: I code at least 5 days a week for a couple of hours, but not always on projects I can consider as part of #100DaysOfCode, and I truly enjoy my offline days. Gives the brain processing space.
- a React app for Museum of Internet that showcases its "archive": a static collection composed of around 10 000 images curated from its Facebook page and its user-uploaded images to the previous version of the site between 2012 & 2019. To facilitate the browsing, the images have been organized into loosely categories. Project link: https://museumofinter.net
- an AngularJS app for Fluidity.Online to showcase Cassie McQuater's Black Room project. The aesthetic is meant to be "the same" as Black Room's aesthetic and the navigation to echo the game. Project link: https://blackr0om.netlify.com/
- a WebGL project for an event happening in Marseille: its metaphorical and about Marseille, the city, plus Pastis, its favorite drink. Project link: https://pastisblood.mutablechaos.com
- The Museum of Internet app was a challenge mainly because of the amount of content, but also in terms of finding a design that is "only" acting ~ For that content. In terms of coding, I've strengthen my React skills and focused on integrating the Sass 7-1 architecture pattern into the app structure.
- The AngularJS app was ~ no challenge ~ I've done it because Valerie aka Fluidity.Online asked me to and I love Cassie's Black Room project. I've used Gulp and mostly focused on code organization after reading a couple of links about "best practices" for AngularJS apps.
- The WebGL project was kinda intense. I've looked at Shadertoy a lot for inspiration and learned to migrate multi-channel shaders from it to Three.JS for it. In order to do so, you need to render every shader to a different scene and pass variables from one to another using read & write buffers. I went through many examples to conceptualize that. One of them was using TypeScript, I found it was much more clever then the other ones. So I've used its structure to implement my project. To compile, I've used Webpack.
In the beginning of the #100DaysOfCode challenge, I aimed to complete a JS coding exercise a day. I've stopped somewhere along the line. Instead, I will dedicate a couple of days to those exercises soon. I find I process better working that way.
The experience has been great so far. It helped me make time for personal projects everyday, pushed me to learn and use new languages and/or technologies.
PS. #100DaysOfCode is a great pretext to code and learn more. I definitely recommend! 💪🙂