Next Move

16 Mar 2018 | Comments | tags: bye

Today is my last day at Domain. After three years, seven months, and three days, it is time to move out.

I will forever be grateful to Domain for bringing me to Australia. Everyone has welcomed this tiny Filipina with open arms, helping me adjust to a new country (there were a lot of trips to the pub).

They also made me jump out of a plane

Our scrappy little app has grown so much over the years. I could never be prouder of what we have accomplished over the years.

We finally get 4.0 🌟!

We were able to share our Developer Story to the world, got a bunch of awards, get recognised as one of the best apps of the year, and launched a lot of features.

I spy with my little eye the Domain logo at Google I/O!

Since joining Domain, I have become a Google Developer Expert, vastly expanded my speaking portfolio, learnt how to bake, and most importantly, met some pretty great people. 😊

What a rollercoaster it has been!

That Thing About Commit Messages

03 Mar 2018 | Comments | tags: git

Last week, I was giving feedback to someone about improving the commit messages they write. I was very taken aback by their response – “it does not matter what the commit messages are”. Now this is confusing for me, mainly because I know from years of experience that having relevant commit messages is important.

Their argument was that change descriptions go into the pull request anyway, so they – not just him, his whole team – do not really care if the commit messages are vague.

I whole-heartedly disagree with this assessment. To illustrate my point, say we are looking for a commit that broke a feature. What I usually do in this situation is to look at the whole commit history to look for anything obvious. It is not very easy when the history looks like this:

😩😩😩😩 We can either go through each of the changed files in each of these commits. This might be too tedious, and the commit messages does not give us any clear idea if that might be the case.

I know this is a super-simplified example, but imagine combing through the history of a repo with five or eight or 20 or 200 contributors.

Going by their reasoning that all the details are in the pull request, I should go into Github and look at all the PRs from this time frame. How many would that be? And would you have to check out each of those branches?

git bisect would be helpful at this point. But if the commit messages were a bit more helpful, wouldn’t we have at least have an educated guess of which commit we are looking for?

By all means, feel free to write a dissertation on your pull request descriptions. Just bear in mind that if you move from one service to another, you would need to move all your pull requests as well. Otherwise you lose all context of your project’s history.

Logan Johnson wrote so eloquently about Square and how they write commit messages. If you are in the “Well that is overkill camp”, then maybe we can compromise by following this tip from @dzaporozhets:

2017: The year in review

09 Dec 2017 | Comments | tags: hello

Welp. Here we are. Another year is about to end.

For a lot of reasons several times throughout the year, I cannot wait for it to be over.

I welcomed the new year in the midst of a throng, freezing in the cold New York night, waiting for fireworks that never came. If there’s a more apt metaphor for the year that this has been, I do not know.

A lot happened this year, including moving this blog from its home of eight years, to shiny new Github pages. I crunched up some numbers and came up with this infographic (thanks Canva!):

That is probably more flying hours than I have ever flown before this year combined :sweat_smile:

A few more days of work and then I fly for the last time this year to Walt Disney World! Sooooo excited!

As a farewell, thank YOU for sticking with me throughout 2017! See you next year and have a great holidays!