Tag Archives: 'vipulgupta2048'

Come along, no time to waste. It’s almost 2 am here, and I want to document this build immediately. Spoiler warning, it took me 8 months to complete this blog.

It’s 2022, and companies still aren’t equipped to handle incidents better.

Incidents can be best defined as a breakdown of a well-oiled machine running on code in a carefully spun environment using complex configurations. Folks in the industry, developers, and customers alike know it all too well. An undesirable phenomenon so common these days that even after years of development, we haven’t figured out how to deal with it adequately. This post is not about how to solve incidents better but handle them well at least publically.  

Back in April, my friend sent me this message on Instagram. And two weeks later, after rushed planning, I was on my way to finally cover these two cities. We cramped so much into this 10-day trip with so little planning that the satisfaction and exhaustion were well worth the effort. Here’s what we did, how things were planned, tips, and essentially me documenting my journey to help others plan their time in the City of Gold.

This is to document some rsync commands, a bash script here and there, and explain to Future Vipul how the backup strategy works for Vipul’s system. Future Vipul is a series on Mixster that I work on to document guides that I need again and again as I work. I firmly believe if even one person gets the help from this guide apart from me in the future then it has served its purpose. I continuously update this guide with more information as my own learning grows and I hope to see you down in the comments if you would like to contribute as well. I wrote my previous Future Vipul guide last year about dual-booting.

#Ask2048 is a short & snappy series of blog posts by Vipul Gupta documenting common questions asked multiple times. If you were sent here by someone, then you are in good company, my friend. Like most things in Mixster, these posts act as a spider web collecting insights from people that have visited before you for the years to come. And hopefully, it will continue to do so as this blog lives on.

This blog is one of the few special posts I have been writing on Mixster in the ongoing pandemic of 2020 before I start my next adventure (Got a Job!) In these crazy times of social distancing, isolation and Ramayana, I rediscovered writing to be something that keeps me calm and composed. I have been looking back at my journey that started with chasing after a piece of paper that would certify that I am a Bachelor of Technology to now being financially independent and content with who I am. Well here I am spilling the beans and documenting my 4 year journey.

Pretty good starter webinar from Remote Indian community, check it out.

Lush green trees, monsoon weather, soul cooling winds coming from the tumultuous waters of the beach where sounds of waves splashing over the dry sand can be heard by people walking by. Now, just imagine a tech conference on a piece of software that powers almost half of the web today at the place that I just described. How could you stop yourself? I couldn’t. Here’s a brief twitter story of my adventures at React India.

Busy servers and applications have a lot of things to monitor and there are stats in several forms. The stats are regarding your servers, applications running on those servers and loads of metrics which needs to be collected and monitored properly. Processing and collecting these stats help in deciding factors like scaling, performance of the system, troubleshooting and among more in your configuration. For monitoring to be precise, the system needs loads of data and the amount of data collected will likely increase the chances of understanding what is happening at any point of time. In this blog, we will be placing two popular collection programs StatsD and CollectD head to head to see what works in diverse use cases, and listing their pros and cons. Let’s go over why StatsD and CollectD are called daemons.