Journal #3

April 25, 2018

So remember yesterday we were 20 minutes late? I’m 40 minutes early today babbyy!! As to why I did that was due to the unbearable heat and death-dirt around my home, aandd I also wanted to prepare for my homework in NIhonggo (Japanese Class) and I’m more productive in an environment where it’s not comfortable to procrastinate and relax.

And so I did my homework for about 50 minutes as my other internship buddies were late. As usual, Jerome was as chill as the summer breeze in somewhere not in the Philippines.

Also, today is the last day for our tutorial sessions with Jerome. Next meeting is with another mentor to talk about Git.

Our tutorial today was a little bit easier to grasp and relatively shorter. We talked about different utility operations that are very handy and useful which can be used in our future projects that we will be working on in the future.

Jerome showed us the techniques of traversing and searching certain files or directories using some quick commands in the terminal (using ack-grep). He also taught us about multiple file handling in a single screen and also multiple screen manipulation.  It’s basically tabs and split-screens in Windows. The amazing thing is how it’s all done in a terminal which still gives me shocks! even to this day.

We were also taught about how to maintain different computer processes in memory, disk, directories, or programs. All for the sake of teaching us the idea of safety and security in terms of reliability and integrity of data or processes.

Another topic tackled was about Web Servers and the service we used was nginx which was promoted as better than apache and is used majority by big corporations and working companies.

Jerome also informed us about the importance of logs and why we should start using and practicing it. He demonstrated how this affects your development process and how important it is to make your life easier in debugging.

We were also given techniques or tips on the future tutorials since we’ve basically covered all the preliminaries of the Linux training. He gave us some tips on database making, database functions, VIM commands that are very useful, and most importantly, career paths and decisions.

Overall, Jerome was very hands-on, he was very patient with us newbies to Linux, and was very understanding that spoon-feeding + some demonstration is the best way to tackle the discussion.

I can definitely say that after the 3 day tutorial, I am somewhat more interested in Linux than in Windows, and I now have some tricks in my sleeves that can be used in the corporate world.

Closing remarks: Training definitely was dragging since we’re new to something and it is presented only through terminal and how it is very tiring for the eyes. But amidst that dragging moment, the learnings learned + the tips given to us was definitely worth it.

12 hours (3 days) down, 288 hours to go.

Let’s see what happens with the Git tutorials this Friday! Hope everything goes well haha!


Journal #2

April 24, 2018

Remember yesterday I was early 20 minutes before the actual tutorial session? Todayyyyyy we were 20 minutes late! It wasn’t our fault though. We weren’t meant to meet on a Tuesday (today) but since our mentor [Jerome] isn’t around this Friday, he asked us if we can meet on a Tuesday afternoon. Tuesday afternoons (1:30 pm) are reserved for our thesis course and so I asked our coordinator if we can go ahead early given that we’ve signed the attendance and she said yes. The problem here is the attendance sheet came late! We were to meet Jerome at 2pm but the attendance sheet came at 2pm! We thought we’d leave earlier so that was our mistake (ish).

Gladly, when we arrived Jerome wasn’t mad or anything. He was as chill like he was yesterday. He was gladly willing to extend until 6pm.

He still didn’t introduce himself and still, we proceeded directly with the tutorials.

We started of with a whole recap with all the topics tackled yesterday as there is a new intern with our group and Jerome felt, which was right, that she be not left out of the group as these topics are very important with the future operations of the company. We reviewed all the topics I listed yesterday and after several hours of talking about it but giving more examples and explanations to it, all of us finally grasped the idea of Linux.

It was very dragging but thankfully my thinking-cap was still on. I was still very interested with the training no matter how repetitive it was. It just gave me the chance to master more what I learned yesterday.

After all the review, we proceeded to something new!

We were taught about the importance of shells and their usage in the computer architecture, and how Linux has a shell that is programmable and efficient compared to Windows. We were also taught how to become a sudo-er in Ubuntu which just means to give us escalated permission without having to log in to the superuser all the time. We also were told about the application manager for Ubuntu and how it has a really big repository with packages ready to be installed. We installed probably 5 or 6 packages to be used (a little) today and in the future.

After that, the main goal for today was Networking. Yes I know that is not very computer-sciency but even I was compelled to learn more about it (as I’ve taken a course about it already) and how it is used in a company setting. We were asked to get our gateway, IP, and were taught about the importance of DNS, ports and port numbers, and SSH.

SSH was the main gist of the networking topic for today. We were introduced on how to connect to remote and local computers within a connection through different commands in the terminal and I felt very techy with it as it introduced a whole lot of possibilities. Truly amazing stuff.

After networking, we were introduced to a little bit of concept called terminal multiplexer – which i guess is a really smart innovation as it gives you a whole lot of security and integrity during remote access. Jerome used tmux and screen and showed us some useful commands and techniques with it.

Before we were again invited to the pantry for some little “snacks”, Jerome asked if we knew the idea of a proxy server, which we did, and elaborated about it and its advantages when dealing with a server.

After that the 6 of us interns mawled the pantry as there were peanut butter, mayo, bread, garlic bread, cookies, and more!, I mostly drank water as I was thirsty and was feeling full after probably 2 glasses of it.

Day 2 was refreshing, and somewhat heartwarming at best because we didn’t feel like total strangers anymore. We were still strangers to everyone but just a little bit. There is this strange feeling of familiarity already and it feels quite comforting and validating.

We were informed that the room that we are staying in with 6 operating laptops, with outlets, great lighting, and airconditioning is fully ours for the whole duration of the internship. We can come whenever we like before the session and stay for as long as there are employees within the building. We were also told not to log in the entrance book anymore so that feels really nice. We are officially part of this company. It didn’t feel this way when we were accepted. I guess it only feels like this because we actually get to notice and appreciate it first hand.

Second day, in short, was nice. Let’s hope the third day doesn’t go bad! 🙂

Journal #1

April 23, 2018

The day started off as I arrived inside the company lobby 20 minutes early. This made me anxious as frick as I didn’t know what to do with myself if ever someone from the company might ask what am I doing there sitting awkwardly in the couch lobby or the panicking question of “do you need something” or just the blank stares of the employees and the numbing crackling noise of keyboards and the horrors of crowd’s murmur and indistinguishable chatters of people – the anxiety just builds up and up and up.

And so, I call out my friends, panicking, with a “where are youuuuuuu” and some “come here fassttt helpp” or what not and not a minute later they all arive, and we are all complete – ready to begin this internship.

We were guided to a white room with a gold brown wooden table that is fully furnished to shine off and reflect a little bit of light to probably (?) show finesse and professionalism. The instructor arrives, Jerome as I learned from other employees, and started off with a quick Hello and yes you guessed it “Do you need anything? water? coffee? etc. ” and of course we all say no because come on, we all are very awkward people.

After hearing the deliberate NOs from the 5 interns (including me), we proceeded directly with the tutorials. No introduction, just directly towards the goal. We tackled a lot of necessary preliminary stuff for the later operational part of the internship especially with handling Linux based operating systems as it has its advantages (speed, efficiency, productivity, and effectivity) against the more popular Windows OS in terms of programming computer applications.

We learned the file structure of Linux vs Windows, the basic commands in using Ubuntu (Linux distributed OS) like how to access, create, delete, modify files and directories, the essence of file paths, how to change or modify ownership of a particular directory, how to change user settings, and how to add a user and set it all up – all throught the terminal. no gui, just pure terminal commands.

We then proceeded to talk about streams (stdin, stdout, stderr), and how these are important and useful in the daily operations in the company as you will need these for logging, testing, executing, and running programs, servers, or any of the sort.

Jerome then introduced us to this “weird-for-newcomers” kind of terminal-based text editor called VIM, and yes it truly was weird as it enforces the user to not use the mouse or arrow keys but assigns the operations of these buttons to certain parts of the keyboard so that your hands won’t be moving as much as before – provides more time and productivity for the programmer. He also taught us about piping and how this is used mostly for programming when you need to pass one result from a certain subprogram as an argument to another subprogram. Something to really look into.

Before we proceeded to our final topic of the day, we were invited to a little snack session with all the company employees. It was VERYYYYYY awkward for me as we didn’t know how to mingle with 25+ years old adult and we were just lingering at the corner of the room talking to one another and barely making eye contact with other employees as we take glances of how they vibe with one another and how they connect and mingle with each other. Our past professor was there and it made it a whole lot more awkard hahahaha because seeing that someone you know sees how awkward you are in a situation TOTALLY brings the perfect package of awkwardness in the room. We called him a lot of times “Sir” as we were accustomed to it since he was our professor and he didn’t want to be called that way as we were somewhat “colleagues” now and there shouldn’t be titles to be said but just first names. not awkward right? WRONG! it was like being pounded down by a million tons of awkwardness and being dragged down to the hell-version of being awkward.

But amidst all that tension, the food was great and the people in the company were very welcoming and jolly to newcomers. They have some jokey-pervert sense of humor but that’s fine. We totally get it.

We ended our snack session and we proceeded to discuss first about company culture. Jerome talked us about how we should find the perfect company that’ll fit our desired culture as there exist a million of possibilities of company culture around the world. Having to choose the one that fits you makes your job a whole lot more easier and fun to work on.

After some lecture and some moral lessons, we went back to technicalities and talked about environment variables and how to modify, add, and access them temporarily and permanently and how useful they are in terms of protecting servers and connections.

A few minutes passed and we said our farewell. We were encouraged to stay but we didn’t. The day was very dragging but it was kind-of worth it as it was spent productively learning something to be used on for the future.

A lot of awkwardness, but a whole lot more of learning. I guess that was the factor that made it bearable for me, something to look forward to everyday.

And hey! awkwardness in a room passes! I just got to have to give it time! So for now, we’ve learned tons and bulkload of information,

we’ll see what happens tomorrow! 🙂

the new era (again)

Starting today, the 22nd of April 2017, this blog will be experiencing a re-branding – a change of what it was purposely made for, a redefinition of what it will become, and a total redirection of where it was supposed to go.

So avid fans, normal readers, bots, or whatever you are, be aware of the new changes. It will be a great one I promise. What change you ask? Stay tuned for the newest blogs coming to you one by one by one by one!

Be shookt, be lit, be turnt! Re-brand, re-new!

The new era (again) is about to begin.


desperation and its limits

The only thing wrong about loving someone is being desperate for their love.

Yes, you were both in love or at least, you were. You would say that you had something going on or that you had something special and that to let go would mean losing something that has already been lost, something which you think is so important that your own dignity and morals would be over looked.

But why, think on this, would you degrade your own value for the sake of attachment and security? You deserve love. You have every right and privilege to be loved back. You have every capability to be worthy of love.

You are and should, and always, be loved – not because you begged, but because they actually, genuinely love you.


And if they don’t, they can go fuck themselves. Save yourself from the pain of walking miles, endlessly, for people who won’t even move an inch for you.


Photos by Kobe Michael

when you fall in love. and out of it. and back again.

Love is kind. Love is not self-destructing. Love is not toxic. Love is genuine.

But love, can also not be love. Sometimes we justify its meaning because we are desperate for it. We tend to fabricate something obviously evil for the sake of having something to feel.

The thing is, and I’ve learned this from experience, it’s better to deprive yourself from love which you have no idea about – those kinds of love where you move towards a path with no source of light or guidance – than force yourself in a moment with a head full of ‘whatever and fuck it’.

Because the worst part of winging it, especially if it’s your first,  is that you will be left in torture. You will be left to force yourself that you were not in love. And as you keep saying that to yourself, no matter how hard you try, there will always be that moment when you hear a song, when you watch a specific part of a movie, or think of a quote, there will always be that moment where you will remember.

You will remember that you were hurt, you were not thinking, or that you were blind to think that “that” was love. You will remember that you were trashed, left, and broken.

And you will remember
that you still remember.

And that’s the worst part, you still, and will always remember something you do not want anymore.

But I guess that’s what makes it beautiful, love is smart. Love is hopeful. Love is healing. When you’re hurt, you learn from it. And when the first doesn’t work, you move forward. I guess that’s why they say your second love is the most beautiful one.

So, no matter what happens, know that love doesn’t stop the first time you try it. It stops when you stop letting it


Feature and Photo by Kobe Michael ->

P.S. I’ve played Andrew Ripp’s When You Fall in Love on repeat while writing this.

to my most mother-like friend

Well, this is a letter to my friend (and hopefully to yours, too? ) who’s like a real mother (duh, title) to me and my group of friends.

Hi, woman.
I’m gonna say this straight up.
I would’ve not surpassed the hardest part of college as of the moment without you.

Although you deserve much of a better intro than that but let’s take it back to the first few days of the first semester of the academic year 2016-2017.

I swear I was in an extremely scary situation where I was venturing forth a place so dark and unpredictable (our college course) where I’ve always felt that I couldn’t make it.

I was in a place where your mistakes mattered greatly especially towards the impact on your future.

I was in a great conflict with myself, a personal battlefield.

But you were there, with me, along with our group. You were there filling the holes in my programming background. You were there cheering me on, building me up, and never, ever, putting that weight of pressure down on me.

You see most people when I talk to them, I feel a sense of urgency to be perfect and faultless, scared of being belittled and underestimated. You, you’re not like that. I don’t know, you just make me feel like its okay to be wrong and you’re here to correct me in a way that it wont make me feel less of a knowledgeable person.

You were there when the school atmosphere felt like a marathon. You were there as an athlete with me, along all the people in college. But you, you were different. We were a team striving to get that gold medal, together – in our own little ways.

And although you haven’t reached the finish line, or you didn’t get the gold, and though you might feel that we’re ahead or you’re behind us, either way. (which you really shouldn’t)

Know that we’ll always be here,
waiting to give you that victory hug.

And before this letter ends, I thank you for everything.
I thank you for your unseen efforts, for your ungratified acts of love (although sometimes you’re a bully/moody), and for you.

I thank you for you.

Thanks, Hazel.
Keep running!

Feature by Kobe Michael ->
(great photographer)
Painting by Hyatt Moore