Note: this blog post right here is post number 500 🎉🎊 so it is a good opportunity to take a quantitative look back.
The daily logs
Since March of 2019 I have kept detailed daily notes about the tasks I have been working on. I used Markdown format and Typora editor, listing everything: GitHub issues, pull requests, meetings, writing blog posts, preparing and delivering presentations, etc. You can find these monthly logs in the repository bahmutov/daily-logs. I have redacted private and confidential information from the source files before creating the repository, thus the logs do accurately reflect my daily work.
You can find the monthly files grouped by year: 2019 and 2020. Every day is level 2 heading, with the items in a plain list:
# March 2019
Every top level item has a category tag. The "official" tags are:
@exampletask for when I created an example or a demo application to show a concept, like examples in the cypress-example-kitchensink and cypress-example-recipes repositories. I also tag most of the work related to the documentation with
@examplebecause our docs do have lots of examples.
@featureis the new code or fixing bugs or writing tests or documenting new feature
@internalare utility tasks that are usually private to Cypress
@supportsupporting our users
@slidespreparing for a public presentation, working on slides, sending a proposal
@presentationthe actual public presentation in front of people
@learningis when I was learning something new
@hiringworking to hire someone
@blogwriting a blog post for https://www.cypress.io/blog/, https://glebbahmutov.com/blog/, or some 3rd party blog
Having these lightweight daily logs helps me during the team's daily standup (copy/paste into the chat bot), or to talk during the ongoing work with the team. It also tremendously helps me to remember the recent items whenever I need a link or a code snippet to share. It also helps me with "Todo" lists to avoid forgetting things I plan to work on in the future. Thus some of the lists are checklists, and it is ok to have some of them unfinished.
- fix incorrect links in changelog 3.2.0 @feature
We can extract the items from Markdown files, group them by tag, and save the totals per month using the scripts in the repo.
I generate counted.csv, counted.json, and even counted.md files. Let's look at what I have done in total over the past year and a half.
The total (%) number divides the total of the current column against the sum of all items (3050) to show the relative number of particular tag. The average number for each column divides the total for each column by 18 months.
You can throw the above CSV into a chart, I like to plot the average breakdown of all tasks by type to get a sense of where I have spent most of my efforts.
Let's take a look at the top three types of work I have done over the past 18 months, and then at the rest.
My top three
Features, features, features
Every month, on average, I worked on 80 items that could be considered "feature work": actual features for Cypress test runner and its numerous parts, build tooling, etc. This number includes the bug fixes as well - anything that touches the code and changes how it works is a "feature" in general sense.
Even better, as the chart above shows, my productivity has generally increased lately. This is due to accumulating a lot of knowledge of Cypress internals and its build steps, and also due to putting effort to bring new features to the users, like component testing which keeps me interested and strongly motivated.
More examples please
My second biggest chunk of work is creating new examples for our users. On average, I have worked on examples 32 times a month. In my personal opinion, no software can be successful without lots and lots and lots examples. We are working on a complex tool, it gets tricky very quickly (unfortunately), and our users will only be successful when you show them how to handle the different test scenarios.
I wanted to do more - yes, we do have example.cypress.io with small examples, and cypress-example-recipes with more than 70 larger recipes. I have contributed to both repos a lot, here is the recipes repo for example:
But we could do more. This is why I wrote cypress-fiddle and made a prototype site glebbahmutov.com/cypress-examples/ from bahmutov/cypress-examples; this project would allow our team to write 10 times more examples than we have right now in a shorter amount of time.
The last top item that has occupied my time was preparing and giving presentations. I have done conference talks, Cypress webinars, and internal presentations at other companies. Every talk requires preparation, on average I have 5 times as many prep tasks (tagged
@slides) as the presentations themselves (tagged
The bottom four
From the report, you can see I don't spend much time in the meetings, interviewing candidates, supporting users, or learning. Let's dig into these numbers a little bit, since they are a little bit misleading.
I can count myself lucky. I had very few internal meetings, under 10% of my tasks. The Cypress engineering process is pretty lightweight, and does not require too much team syncing. Thus the
@internal items are only occupying a tiny percentage of my weekly activities. It might change in the future, as the company is growing. We will see.
Another interesting trend relates to hiring. I have joined Cypress 3 years ago in May of 2017 when the entire company had only five people. As we grew, I had to interview a lot of people to hire for every engineering position. As we reached our current size, the need to personally interview every candidate disappeared. Thus I could spend more time writing examples, while essentially stopping interviewing in the recent months.
There are very few items marked
@support - not because I do not answer users' questions in Cypress chat or on Twitter, or via GH issues. I answer these public questions a lot, usually by sending links to examples! Thus I would mark work to create a public example and send it to the user as
@example. Most of the items marked
@support is an actual user session with our Cypress users due to some difficulty in setting up Cypress in their environment, or running into a problem in a specific app, etc - the paid support.
Finally, the tasks marked
@learning are honestly an undercount of the daily stream of articles, videos, and tutorials I go through. I just don't always remember to add them into the daily log. I would say about one or two items per day should be in this category, but alas I don't have a record to support it.
I am lucky to do most of my work in the open using mostly public GitHub repositories, issues, and NPM packages. Thus one can see (mostly) everything from the pas 18 months in the table below.
|Month||GH||Commits||New repos||PRs||Reviews||Opened issues||Total||Level|
Total = new repos + PRs + reviews + opened issues
We take the first month of March 2019 as the base level of 100% and normalize the GH work against that month.
Level = month's total / 138 * 100
Let's plot the Level column. I see a mostly productive 2020. I have skipped August 2020 since I am taking a couple of weeks off. August 2019 is also a "down" month since the entire family went on a trip.
The daily logs and the GitHub activity are in agreement with each other - compare the above contributions chart to the "hiring vs examples" chart - the overall shape of the red example bars matches the GitHub activity chart here.
I love my open source work at github.com/cypress-io and in personal repositories github.com/bahmutov. I hope my next 18 months are as productive!