musings

    Death Stranding is an open-world game with beautiful landscapes set in a post-apocalyptic America. The game's design forces you to manage every single resource. You need to arrange each tool and equipment, carry weapons, go number one and number two by yourself. The player also needs to plan each step they take as they traverse the world. I mean step literally, as in left foot forward, right foot forward. You can also look into the mirror with your character and admire your face. I'm pretty sure no one asked for that feature. In short, DS is a walking simulator with a really weird story. The main campaign can easily take you more than 40 hours to complete. But damn the game is so boring. DS is accurately described as a walking simulator. Despite all of this, a legit argument can be made that DS is a masterpiece. There are many awesome video games and I think DS also belongs on the Mt. Rushmore of videogames.     The  Death Stranding  is a cataclysm...

       There is a reason why most of us are more comfortable using Windows and other graphical user interfaces. Interaction with digital objects comes naturally. But what if you land your first job and you are required to get comfortable in the terminal as soon as possible? Or do you find yourself in a situation where you cannot use a computer mouse for some time?  I am putting together a comprehensive introduction to how adjusting to living in the terminal is like. I want to introduce some indispensable tools every shell scripter uses. What does it mean to live in the terminal? A lot of operating systems have graphical user interfaces. Of course, GUIs are beautiful and interactive but developers need to be as productive as possible. Living in the terminal means being able to execute your workflow right from the terminal with minimal use of the mouse. To start living in the terminal, you should get comfortable using vim as your default editor. Using nano is ok, ...

  How to resolve commonly faced issues The purpose of this guide is to provide some guidance to troubleshooting some recurring issues on the development server. Possible trouble areas Frontend  Git workflows Voice Telephony Development servers Everything is logged on a development server so as a general rule of thumb always check logs if there are any to assist in finding a solution. For example, if it is a PHP log, it is likely to be found here: /usr/local/apache/logs/error_log Frontend Let’s say that you’re unable to access the web page due to a “Whoops Error”. There could be a number of reasons. If the stack trace includes [STALE WEBPACK-MIX ASSETS], running  yarn install --check-files && yarn prod  on the development server will safely bring the web app back.  What actually happens Yarn will fetch and rebuild the web assets and you should be able to use the web application afterwards. What if you’re still unable to access the web app? Sometimes p erf...

I first heard of Nietzsche from Sister Rita Mishael, the strict librarian at my elementary school. I'll refer to her as The Librarian from here. I was fortunate to have such a learned librarian. She also took us through Christian Living, for she was a nun. Her teaching notes were always sprinkled with quotes from various philosophers and psychologists.   I didn't always like The Librarian. The first time I interacted with her, she made a remark that my parents didn't bring me up properly. It stung so much! I, for one, made sure to register my displeasure. And of course, she didn't like me either. All the students found her accent weird and we made fun of her accent any chance we got. I'm quite certain it infuriated her. The Librarian made it her life's mission to instil discipline in us. Children are always bound to resist and this didn't make it easier on any of us. I wasn't a rowdy boy or anything like that, but I did share the same distaste every othe...