(not a) former GitLab Developer Advocate,
Ruby on Rails apps architecture explorer
Painless Rails - A book describing the painless way to deal with Rails. Yes, it's 2018, but we still have too many unanswered questions in the Rails community which need to be answered.
Tabsqueeze - solves the problem of too many tabs in your Chrome browser. Like OneTab, but better. It squeezes selected tabs into shareable links in one click.
Strftime.guru - Converts date/time samples into format snippets for
strftime function: "9 Feb 2018 19:31:44" → "%e %b %Y %H:%M:%S". You don't have to remember or google for it ever again.
1Activity - an application for macOS that helps you pre-organize your downloads based on your current activity.
Hamdown - markup language proposal; basically a mix of Markdown and HAML to get the most out of both formats.
GitLabFan - my one-year-old stealth project - basically a collection of illustrated articles about GitLab.
GitLab CI course - interactive course to help you get started with GitLab CI.
One and a half year have passed since I no longer getting paid by GitLab. It was not my decision to leave the company, but I couldn't imagine that I’ll become GitHub or BitBucket developer advocate, for example.
There were two reasons I applied to GitLab Developer Advocate position. At that time we moved to Serbia, I started to give talks at European IT conferences, and I wanted to do more of it. I thought that it would be good to get paid to do more of what I wanted to do.
The second reason was less mercantile. Once I considered such an opportunity for myself, I made a research about GitLab, and my mind was blown. In a few years, GitLab turned from a questionable open source clone of GitHub into a great product with an incredible vision of new.
I fell in love with GitLab. I’ve become a true GitLab fan, and I think it was even a disservice for me - sometimes I was too biased.
Anyway, after I was no longer in GitLab, I didn’t feel that I have stopped being GitLab developer advocate.
So I had a dilemma what to write about myself in social network profiles' descriptions. I decided to stay with “Developer Advocate of GitLab”, but it sounds weird, and I was uncomfortable about it.
Moreover, whenever I speak at a conference and mention that I am a former GitLab Developer Advocate, people’s brains simply skip the word “former”, and they keep thinking that I still work in GitLab :)
It was not without me giving them a room to think like this, because nothing has actually changed in my behavior after dismissal.
And it was pleasant to hear from Dmitry Zaporozhets recently, that I am still doing a better job of advocating for GitLab than he does :)
It took me a while to realize that you don't have to work for GitLab to call yourself an advocate. I love GitLab as a product, I like GitLab's vision of the future, so let’s make it official.
Today I am changing all my profiles description to "(Not a) former GitLab Developer Advocate".
Go sue me, GitLab! :)
P.S. And yeah, now I am back again on the mission to give out all the GitLab business cards I have. And I still have quite a lot of them:
June 6, 2018