Daily Logger Recap
As devs, we all have things that make our day better, right? For some, it's coffee, for others it's listening to some cool or deafening music while coding, etc. For me, one of those things is automation. Less repetitive tasks. Especially when dealing with social networks. I Do Not Like Social Networks. There. I've said it... However, there are some things that are really helpful. In my case, one of those things is the #100DaysOfCode challenge. A big part of this challenge is to log your progress daily, in public, to push your limits and to be part of something better than yourself. So. When I started this challenge in early March, I immediately had the idea for my first project: a daily logger. That way, I wouldn't have to write a posting on Twitter and one on Github each day. I wanted a small, simple page where I could simply enter my daily progress and it would output a carefully formatted Twitter post and a Github one. I thought "simple first", so I went for a vanilla js solution with only HTML anc CSS. You can try it here or check the code.
The result worked for me, even if it wasn't as reactive as I would have liked it to be. We needed to enter all of our information, then click on the
Let's Go button and... that annoyed me a bit. I felt like it could be so much more!
At the time, I hadn't touched React much outside of tutorials. However, having taken on the challenge and feeling like there were so much that could still be done, I pushed forward and, greatly inspired by the teaching of Brad Traversy in his MERN stack course on Udemy, I dove right into a big project: a MERN migration of my simple page.
So, all pumped-up, I rolled-up my sleeves and created a project on Github. I created issues after issues, classifying them in my Next | In Progress | Done | Not Doing categories as I progressed. It felt good! It felt like... work! But I mean that in a good way! I would branch out of master and work on bringing in a feature or two, then make a PR and merging when all was good! I liked the whole process. A lot. I promise that I will keep on working like this, as I feel like it's a much safer way to progress on a codebase, and also because the industry works like it, right? It just feels right.
project done, time to showoff
When my project was completed, I was very happy. I felt like I had gone from something simple, into a complete fullstack application, learning a ton in the endeavour. So I went on to make a documentation page and a demo of the app on Github. I felt proud. I still do!
Of course, the code is not perfect. After all, this is my first complete web app. I will revisit it later on to trim parts of it here and there, of course. It's just natural that I do this, in order to fully complete the circle.
I use my app daily, so mission accomplished! Now, even though I could have pushed it live, I decided not to publish it. For many reasons, but the most important one is that I don't have time right now to maintain it in production. That said, I'm not discarding the possibility to do it later on. The last commits I made brought a better security layer on the API, so it could be quite decent out there. But, for now, status quo.
It was such a great ride. I feel like I have learnt a lot in making this app and I look forward to making my next one, which will also be in the realm of the useful applications, for I find that this is what gets me going. I need a challenge that I know could solve a problem once done. Of course, since I still consider myself as a beginner in the field, I know that there are already a lot of tools out there, however I find that in designing one myself, I learn so much more.
And that, my friends, is what drives me.