Skip to main content

I am a lead frontend engineer at Tinkoff. This is a personal blog, views and opinions are my own.

Code Review: the Small Things and the Big Stuff

Code review is an essential part of software development. It is a process where peers review code written by their colleagues to find bugs, ensure quality, and maintain code standards. Most new developers assume that the code review’s only purpose is to find bugs, but in reality, it is much more than that. It is a place to ask questions, to bring the code up to the team’s standard, and to check if the overall architectural decisions make sense.

[#non-tech] Big Gay Loneliness

This study is not scientific in any sense of the word, nor does it claim to be. Moreover, being deeply subjective and expressing not objective truth, but the author’s own deeply biased views and experiences, it should be read more like a work of fiction. Again: my aim is to mostly talk about personal experience. Generalizing it and writing in third person makes more sense to me at this time.

Web Vitals: Metrics & Tooling

Web Vitals is a set of ±10 metrics compiled by Google’s internal team to assess and quantify web page performance. The value of this particular set of metrics, and the reason it’s popular with frontend developers, is that all of these metrics have a direct impact on the user experience of page visitors. This means that if we improve these metrics, we are objectively improving the experience of users visiting our site.

Jest Snapshot Testing: a Blessing or a Curse?

My current project at work is a React app. I’ve joined this team only a couple of months ago, but I’ve been happy to learn that my new colleagues have been considerate of the code quality: the codebase is 100% TypeScript, excluding some Node modules, which I always prefer over JavaScript, and most of the components and helper functions are covered by unit tests, which use the Jest framework. At that moment in time, I was new to Jest.