Hi! I’m Vlad GURDIGA. 👋🙂
It’s good to have you here. Here I’m writing mostly on thechical subjects, like UNIXy stuff, vim, and GNU make, but I also touch on productivity and personal development.
I have a more or less ancient iPhone SE 2016, with 16GB of storage. For the past year or so, the storage was filled up to 15.5GB most of the time. I kept juggling the apps by offloading and restoring the ones that I only needed once a week. Lately, some of the apps that I use grew past 200MB in size, and I got to a point where I just didn’t have enough space.
If I were to give a single piece of advice for easier journaling it would be this: make it handy.
Last week I helped a friend move their blog subscribers from FeedBurner to Follow.it.
The other day I found myself in a conversation where I was recommending journaling to improve self-awareness and the capacity to analyze issues small and large. Then as I thought about that conversation later, I realized that for someone who didn’t journal for at least some time, it may sound too grandiose and unapproachable, and so I thought that I should have suggested an easier way to begin. After that, this idea was bubbling again and again in my mind, and so here I am explaining it here.
On my 30-th week of Angular, I learned something that I was looking for since the first week: a lightweight way to get a “parametrized” piece of view. Coming from a couple of years of React, I was used to having function components to abstract away noisy bits of a view, and for some time I thought the only way to get that is to get such a thing.
Here is a small post about working with small companies.
Every now and then I end up in a messy codebase. It’s scary and discouraging to try to fix a bug in there.
I have recently switched jobs. This is the main reason why I haven’t written on my blog for a while: I wanted to focus on getting familiar with the new household.
In 2014, I wrote about a couple of things that I liked about Angular, then at v1.4, I think. Now, as I’m getting on Angular at my new job, and I’d like to share the things I like again. So far, the concepts seem familiar, and I will only comment on the things that jump at me, from the perspective of a newcomer.
I’m a heavy console user and I like my shell history to be relevant to the project that I’m working on. For example if I
~/src/mixbook_editors, I want the shell history for that specific project—this is what I mean by per-directory Bash history.