New Year, new projects to work on.
With the new year being here, I have some new goals that I want to complete. One of which is coding every day. So this year, I have decided to create Project 52.
Why Project 52
The goal of this project is to create something every week. Yes, every week. The projects could be big or small; it doesn’t matter as long as I build something that I am interested in.
So here is how this is going to work.
- I pick a topic. It could be anything.
- I recreate something cool I saw or create something that is entirely new.
- I get to work on creating the MVP.
- At the end of the week, I have to post the project in its state.
- It must run and do something.
For more information, you can check out the repo where the projects are being stored.
Why Should You Care
Now, why should you come and join me in this process of building projects?
You would get to see the process of me building something. Not one-off projects that never get finished but small mini projects to test ideas and see where my coding abilities go.
The second reason is that you guys like me or something. Yeah. I honestly don’t know why you would want to watch me do this. I’m just a guy on the internet. But this is important to me.
But mostly, I was inspired by this YouTube where he created 52 projects in a year. So why can’t I do the same?
I also want to be those developers that code every day and have those big, fancy, all-green repos. I think to love something so much and do it every day is really admirable, and I want to emulate that in my work as a developer.
The First Project
Now, the first project is something you don’t have to wait on, but it is done and dusted. I decided to start small with a CLI tool. This tool is similar to neofetch but really, really bare bones. It’s the project from this roadmap. It shows the CPU, RAM, and disk usage. It also shows the top 5 processes for CPU and disk.
This was a pretty fun first project to make as the first entry to Project 52. I was able to learn about a tool called top, and that is what I leveraged to make the CLI tool.
top -n $numberofprocess | head | grep $filter
The program works by calling top, filtering down to the number of lines I need using the -n flag, piping that output into head, and then piping it into grep to filter for the specific lines I needed. I printed the final output to the terminal, which is how I got the results shown above.
More projects to come. The next one should be really cool.
Top comments (0)