I'm writing this for new teams and individuals I start working with. Our initial conversations often revolve around the projects I'm involved in and the specifics of my craft. I'm trying to explain what we're creating and how we're doing it.

However, these discussions usually entail an overwhelming amount of information, too much for brief coffee catch-ups. Consequently, I invariably omit discussing my personal work/life principles due to time constraints. As a result, people gradually learn about my working style over the following months.

Admittedly, my work principles have their challenges and are far from perfect, so I am actively working to enhance them. If you're reading this, I aim to bypass this initial awkward phase, allowing you to understand more about what I expect from others and what you can expect from me. If you have a similar document, feel free to share it with me :)

**System bias**

I greatly respect individuals who establish effective processes and strategies for their products. This includes companies succeeding at long-term planning and delivering interconnected systems. The same admiration extends to companies creating books/games/movies with universes whose lore remains relevant and evolves over decades.

My expertise lies in UI development, design systems and tooling. I've been working in this domain for a long time, often dealing with the aftermath of initial decisions and correcting my own mistakes. This experience made me biased toward treating many things around me as systems. While I acknowledge that not everything requires such an approach, it's useful to consider whether something will need ongoing maintenance a year from now. If the answer is yes and there's no plan in place, it often leads to either a complete overhaul or a continuous, costly stream of work. My goal is to preemptively avoid such pitfalls.

Building systems is undoubtedly costly. Therefore, I dedicate much of my time to improving my ability to develop systems quickly without compromising on quality and helping others to build the same skill.

**Controlled chaos**

Over the years, the principle of playing long-term games, which requires extensive planning and time, has become central to my approach. My aim is to make system building more cost-effective and rapid. Consequently, I often find myself in a state of "controlled chaos."

I typically manage several projects simultaneously, allowing me to switch between them based on my current mindset, much like choosing a book to read according to one's mood. This flexibility lets me focus on work that most effectively contributes to my goals.

In my work environment, the pace is as crucial as the underlying processes. However, I am willing to forego certain processes if it means achieving faster progress. Any approach or tool that saves time becomes an integral part of my workflow, even if it's not a standard practice within the team. While some of these methods may not always be well-received, I use them independently. Sometimes, these methods prove beneficial for the entire team and are adopted into our collective workflow.

**Transparency by default**

I firmly believe in transparency. I make every document I create accessible to the entire company, unless confidentiality is required. You can ask me anything, and I'll provide my honest opinion and all the information I have. This approach greatly simplifies interactions, ensuring everyone involved has the same understanding. If not, a single shared link can bring everyone up to speed.

Additionally, transparency has proven invaluable in mentoring. By consistently investing time in writing and maintaining openness, I encourage similar practices among colleagues, fostering a more effective work environment.

**Fighting for simplicity**

I always begin my work with a blank canvas, considering the end-use of my solution. This mirrors the principle that "the best design is no design." In a similar vein, my philosophy for building systems is "the best API is no API." Ideally, a function should require no arguments.

This approach allows me to encapsulate much of the system's complexity, offering more flexibility, especially for future, unforeseen requirements. Even after finding a solution, I persistently question how it can be simplified, aiming to shift complexity away from the end-user.

Another perspective is that not all problems need a complex, systematic solution. Crafting simple solutions is also challenging, and sometimes the best approach is direct communication or allowing time for the problem to resolve itself.

**Inbox zero everything**

I place greater trust in my software than in my memory, so I always write things down and care about keeping them up-to-date. It's essential for me to rely on my tools to swiftly access information, avoiding the need to burden my memory with unnecessary details.

Because of that, I treat every information storage as an inbox. This includes my email, calendar, Notion, and other platforms. I instantly review all notifications, quickly decide what information to retain for future reference, and aggressively eliminate anything no longer needed. This system helps me stay organized and efficient.

**Notes**

* I'm an introvert when it comes to large gatherings of random people or people who don't have similar interests. But I do appreciate conversations with small groups of people, especially if I don't have to come up with a topic to discuss. This translates to work as well. I am more interested in deeper tactical discussions in smaller groups than in involving everyone into wider discussions.

* I spend a lot of time online and quickly respond to all the notifications. That's not always good for me, but I still prefer working like this over having many things left unprocessed. This ultimately gives me peace of mind.

* I put a lot of effort into supporting other people as long I see them showing initiative. You can ask me for help and I’ll do my best, but if I see no effort coming back – I will stop immediately.

* I'm a slow thinker. That makes it harder for me to work with people I've never worked with, but that's how I operate. The second meeting with me is usually better than the first since I had time to think about what we've discussed.

* When a project needs me to play different roles – I will do it. People don't necessarily have to ask me about this. More importantly, I will do this if I see people not delivering the work. I care about the work done more than the processes and defined roles.

* Humor is the way I live and work. The more sarcastic jokes I make, the more I appreciate the people around me and trust them. I'm also in the same boat and ready to be on the receiving side of these jokes and laugh with the group.

* I like changing the surroundings and staying in a dynamic environment. That helps me feel the life through people around me even if I don’t interact with them. When I work, you can frequently find me at random outbreak zones or a coffee area.

Dmitry Belyaev

Work Experience