Opinion

You have to be a psychopath not to worry about uncertainty

November 30, 2024 Opinion No comments

The other day I was asked if I was worried about uncertainty. This was asked in the context of some ambiguity in our 2025 plans at work. Here I just want to share some of the thoughts on the topic.

My answer was: “A person has to be a psychopath to not worry about uncertainty at all. We, as humans, seek safety and security. At the same time, the biggest of our successes come from uncertainty and taking risks.” (*)

Not knowing what to choose is one big source of uncertainty and anxiety, the drain of indecision takes out your energy and you get stuck in dreaded “analysis-paralysis” . The reason for this seems to be our nature of being afraid to lose something, even if it is a prospect of future opportunity. For instance, you might have a possibility to get promoted in the current team, which you will lose if you switch to another team.

Do you know the origin of the word “DECIDE” ? It’s from Latin decidere which combines two words: de- ‘off’ + caedere ‘cut’. Yeah, to decide, we have to cut off something.

I took some risks (changing jobs, moving countries) in the past and believe I was rewarded for taking them and had some failures in other cases (financial setback on home purchase). I was wondering if there is a sure way to deal with the feeling of uncertainty and that grueling waiting time between making a decision and knowing the outcome of that decision.

Taking inspiration by thinking about people who dealt with risks and uncertainties isn’t always helpful. Popular culture is overhyping people who succeeded by taking risks – please know that for every single billionaire out there who miraculously made their startup successful there is an ocean of people who failed. Survivorship bias in play (**).

Thinking about people who have to deal with major uncertainties right now doesn’t help either. For instance, many of my fellow Ukrainians face uncertainties of the unthinkable levels, they lose homes, jobs, loved ones, and the future is unclear. Objectively my uncertainties compared to theirs are negligible.

Rolling up the sleeves and just getting into the flow of work and just being in that mode of constantly solving problems and mitigating risks helps as long as you can maintain that state. I see this as a mode of “fight” in a survivorship physiology (***) – fighting is cool and can get you far, it’s just that sustainability is difficult.

It appears that the easiest to deal with uncertainty is multi-fold: having a very solid safety net, having a streak of risk-reward successes that gives you confidence boost (think of emboldened territorial lobsters (****)), and actually enjoying the process itself. But all in all, you just have to embrace the uncertainty as something natural and impossible to avoid. Absolute 0 uncertainty means you are dead – I will get to it.

There is this concept of the cone of uncertainty often used in  risk management. The idea is fairly simple – as the time passes more and more risks are either realized or mitigated and eventually residual risk reaches near 0. In the context of project management this happens closer to the project end. I have joined many projects where it was absolutely unclear what I had to do and how the things will evolve, few months in and it gained some structure in my head, few more months and there is a feeling of being on top of the things, and eventually few more months in it is all done and ready and you are on the outlook for the next big thing. So, my friend, don’t worry, embrace the uncertainty and deal with ambiguity, as they say.

In our lives the moment we are born the uncertainty of what will come of us is the highest and as the time passes we become who we are today with the uncertainties of today. Now to sound overly morbid, we reach a personal level of 0 risk at the time of our death! So enjoy non-0 risk and uncertainty!

There is more to come ;)

What are your thoughts on risk, decision making, and uncertainty?

Footnotes

(*)To be fair, taking risks presumes that there is a possibility of failure, which does happen, otherwise it wouldn’t be a risk.

(**) https://en.wikipedia.org/wiki/Survivorship_bias

(***) Look at the middle section from this diagram of transitioning from Polyvagal theory: https://equusoma.com/wp-content/uploads/2022/03/The-Polyvagal-Defense-Hierarchy-2021.pdf

(****) This is a bit silly but every time I think about repeated successes or failures I imagine territorial lobsters analogy by Jordan Peterson: https://www.youtube.com/watch?v=5ZOkxuNbsXU


No comments


Building a Learning System

November 18, 2024 Opinion No comments

In the past I wrote a few posts on learning, specifically this one, where I talk about the learning pyramid in which teaching someone has the highest retention rate followed by practicing what was learned, followed by other methods of learning (visual, audio, reading). I also have a quick overview of a book “Learn Better” in which the key premise is that learning is a skill you can teach yourself to be better at.

Not long ago I was also asked if I have a learning system. I don’t. In fact, I clearly remember how inefficient I was at learning in university by trying to memorize some mathematical proofs instead of properly understanding them and recreating when needed.

So what a good “learning system” could look like?

Purpose and Value

I think a key to good learning is genuine interest in the topic you are trying to learn. Interest could be internal curiosity or simply seeing value in learning something specific. To give few specific examples:

  • I rock climb as a hobby. As such, taking outdoor courses, reading books on climbing just comes naturally for me and I don’t have to force myself to.
  • After joining Google I had to refresh my rusty C++ knowledge, so I had somewhat practical motivation to learn/refresh knowledge, but it went well.
  • When I moved to Austria I had to learn some German, but it really was forced on me and I didn’t make much progress, but did minimum for required paperwork.

What to Learn

Now, if you are intentional about learning, say for your career, probably the first question you have to ask yourself is “What should I learn?”. These days the amount of information and resources available is just incomprehensible to our brains. As such, being selective and strategic is important. Think what would make most sense to learn in your specific situation so that there is purpose and value for you.

Deliberate Practice

The highest retention of knowledge is when you teach someone or immediately practice what you have learned. I always like to think about learning as neural pathways in your brain, when you consume new information you stimulate only one direction of storing the information, but when you practice something or try to teach someone you stimulate and reinforce the retrieval direction from the storage. 

If I had to create a learning system, I would prioritize practicing as much as possible. The fastest way to learn might be to learn “on the job”, but if this is not possible, the next best thing might be to set SMART goals (you know the drill).

Consistency

One issue that comes up with learning something is sticking to the plan. Consistency is hard, it really is. For myself, I found that accountability, periodization, and re-inspiration are the best ways to stay on course. This weekly blog post writing is part of accountability I have. I try to re-remind myself why I’m learning something and also trying to get inspired by other folks.

Summary

So what does my learning system look like? 

  • Purpose: Genuine interest or practical need.
  • Focus: Be selective and strategic in what to learn.
  • Practice: Teach or apply knowledge to retain it.
  • Consistency: Use accountability and inspiration to stay on track.

What would your learning system look like?


No comments


Intimidated to try something new? How discomfort opens doors

November 2, 2024 Opinion, Success No comments

Everything in life happens for the first time (and last time for that matter), but some things don’t happen at all. First kiss, first job, first home, first kid, first gray hair. Success isn’t guaranteed and failure isn’t unavoidable.

There is this martial arts dojo next to where I live. I used to walk past it and see people practice.  I never did any martial arts so it was very intimidating and uncomfortable to sign up there. Everyone appeared many levels above me, and true I would get punched in the face during sparrings. Year and a half past that I have fun and feel super comfortable during our light fights. Outside of the gym this gives a psychological sense of security (it is a false sense to some degree, though, but the effect is there).

Me with Kathy Long in Intention MMA DoJo in Vancouver

I have never been to any sauna until maybe 30 years old. I always thought of saunas as some weird place where completely naked people sweat, so it was very uncomfortable to go to sauna at first. Now I can easily outsit many people there. I love saunas.

On one of my recent work trips there was a junior engineer on our team who would strike up a conversation with everyone, literary. It was amazing for me to observe this person: while buying coffee he would chat with a barista, he would join a random group of colleagues to chat about whatever. I mean, I have seen many extraverted people, but this was another level, so I followed his example and pushed myself to talk to strangers. On the flight back I started talking to a person next to me and had a great pleasurable chat that killed the entire flight’s time. This is because I pushed myself into discomfort, not because it was natural to me.

Being in a senior position at work requires stepping outside of comfort and talking to a lot of people I see for the first time. I have been observing how other leaders are doing this. I found that for myself I need to imitate what they are doing. The behavior appears to have common and fairly simple patterns: being respectful, thanking people for what they do, catching the essence of the message, speaking but also giving others opportunity to talk, etc. Topic for another discussion, but pushing yourself to be more like a leader makes you a leader.

You need to sign-up to give that presentation at work, you need to have that uncomfortable discussion, you need to pick that daunting project, you need to step outside of your comfort zone and embrace the challenge. Growth only happens when you stretch beyond what you already know or what feels safe. Biggest successes in life come from risk taking and discomfort! (yes, there is a chance you will fail, otherwise it won’t be a risk).

This blog post is mainly a short self-reminder about the importance of embracing uncertainty and intentionally stepping into the discomfort territory. Do it – you will emerge stronger on the way out.

I signed up to showcase my rock climbing hobby at work during DEI&B fair next week. This is a bit uncomfortable, let’s see how it goes. More to come…


No comments


What I don’t like about meetings

October 19, 2024 Opinion, RandomThoughts No comments

I estimate I’ve been to 10k (*) meetings in my career (holy smokes) and I’ve never written a blog post on meetings, so here it is. There are tons of recommendations online on effective meetings, things like having an agenda and setting goals for the meeting, inviting only necessary attendees, etc. In this post I would like to highlight just a few things that I think I might be doing differently and I will bring them in light of what I don’t like about the meetings :)

“What are we discussing?”

Let’s start with this: I really don’t like when people call for a meeting and don’t provide even a line of context or agenda. First of all this doesn’t give me or others means to properly prepare for the meeting. Effectively by not providing context or agenda the organizer is robbing themselves of a chance that some attendees will have more to contribute to the meeting. Additionally there is a good chance the meeting will be hijacked. In my view not having an agenda shows a grain of disrespect because the organizer demonstrates that this isn’t something important to them either.

  • DO: Always, always add a bit of description to the meeting invitations you send. At a minimum say that the agenda is coming if you need more time to prepare but have to book time. But most of the time target creating meeting notes documents and adding context, agenda and any relevant info to the doc.

“So what was the decision?”

Another thing I don’t like about meetings is when there is not a single output artifact. After such a meeting, I’m asking myself “What was I doing here?” Lately I started solving this problem by just starting to take notes in meetings independently of my role in the meeting. If no one is presenting their screen I will just silently start sharing mine with notes being taken. I’ve been thanked on multiple occasions for notes that appeared out of nowhere. I’ve also been complimented for keeping the best track record of 1:1 or other discussions where I play a more active role.

  • DO: Always play a role in the meetings you are attending. If noone is taking notes, take them yourself, if no one prepared an agenda/context but you have context – just create that doc. Maybe request the organizer to add the notes. Just 5 min of your time could make the meeting go in the direction you want it to go. Yeap, this is because by sharing the screen and people reading the context and agenda you put they are likely to follow some of that even if they are 2-3 levels above you (you can influence without authority in such a “weird” way). For big townhall kind of meetings, always attempt to prepare one question, this will keep you engaged in the meeting, otherwise just don’t join.

“That could have been an email!”

Oh, I also don’t like long or “that could have been an email” meetings. You know, those where all the useful information has been shared and discussed in the first 5-10 minutes and then people just chat about related topics and say they need time to think about it and respond, meaning that if it was an email the course of action would have been the same.

  • DO: Well if something can be shared/asked via email just do it. But if you have to have a meeting schedule just enough time for what has to be discussed. You will be pressured to arrive at a conclusion within time you have and if you really need more time just schedule a follow-up. I found that 30 minute meetings are almost always enough.

“I want out of here.”

Oh, how about the “fill the void” where you feel like there is pressure to say something? In these kinds of meetings those who like to speak a lot take pleasure in just speaking and speaking and those who don’t like speaking secretly cannot wait for the meeting to be over.

  • DO: If you are leading the meeting, encourage people to speak so long as new ideas are flowing and value is being added. The moment things become repetitive, same people talk non-stop, or there is disengagement, consider concluding the meeting, no shame in that. If anything people will thank you.

Conclusion

Unquestionably we need to meet at work. The purpose of meetings is to add value, help arrive at decisions and drive progress. The things that frustrate me the most, like a lack of agenda, no clear outcomes, and unnecessarily long discussions, are often avoidable with just a bit of effort and intentionality. By always preparing an agenda, ensuring there are actionable takeaways, and taking control when needed (even as a participant), you can influence the flow and value of a meeting.

(*) 16 years x 52 weeks x [5(early career) – 20(later career)] meetings/week = [4k – 16k]


No comments


Level Up Your Work: Why Documenting Everything Matters

September 28, 2024 HowTo, Opinion No comments

If you are in a knowledge job, do yourself a favor and document everything as if your activities and thoughts were relentlessly producing logs similarly to a production server. Make it a habit and develop it so it becomes second nature. Offload cognitive burden to your computer, you don’t need and won’t be able to hold all of that information in your brain.

Let me give some of my personal examples and then follow up with how this was useful to me and others.

My tax documents from when I was a self-employed contractor

1:1 meetings

We all have 1:1 meetings: with our managers, peers, other stakeholders. I have a running doc for each individual person and take notes of every work conversation. For every person I create a go-link (something like go/person-andriy). This helps in 3 different ways:

  1. Adding topics. Every time I think about a topic to discuss with someone it is basically very keystrokes away. never have to go over the mental struggle of “Oh, what was that thing I had to talk to them about?”
  2. Searching for info. This one is probably obvious, but just to emphasize, I think our memories work by association, and it is often easier to look up something if you have a person in mind for a specific topic.

“Talk to X” docs

I extended this practice of storing topics for conversations into my personal life. I’m usually not documenting conversations themselves as they happen over coffee or walk and it would have been super weird to type during those. At the same time those docs work as a quick refresher and I found that in most cases this hugely enriches my conversations.

Cross-referencing everything

Cross-reference! cross-reference! When writing documents we obviously reference the sources of information, but a step further is to also do it in reverse (if possible). This helps connect the information and traverse it in any direction. So, if there was a strategy created based on a dozen of discussions with multiple teams, adding a link to that strategy to each discussion’s document will help each team relate to what that discussion has led to.

Documenting before and after religiously

A new practice I picked at Google is to capture “Landed Impact” in the design document after the actual launch. A design document would normally have effort justification, which often includes expected impact, but then “Landed Impact” would capture what actually happened. And I keep adding to that section. As a very specific example, I finished a project that reduces the monetary impact of outages a couple of years ago, and relatively recently there was an outage that would have cost us a lot more money if that project wasn’t done. I simply went to that old doc and documented this more recent impact. Why spend effort on this? Here we go:

Artifacts pay off

Presence of good artifacts makes a huge and oftentimes decisive difference to the outcomes of performance reviews and promo discussions. Think about the promotion process, you cannot even imagine how the presence of solid artifacts is important. With the artifacts in place people don’t have questions, they are like “here is the impact, here is leadership, this is influence, SOLID case”. Instead if artifacts are sloppy it becomes hard to drive conclusions from them, people are like “scope of work is unclear, impact might not be for the next level”. With good artifacts you are offloading cognitive load not just for yourself but for others, you make their decision process easier and they also feel like their responsibility is taken care of.

Unfinished work

Do you know those dreadful situations when a project is axed? This could be in your control (you didn’t find enough impact in work) or outside of your control (reorgs made this part of thing irrelevant, it is too late to market). Are a few months of your effort all waste? Nope, if you documented the learnings, basically you have your retrospective and learnings document ready. You hand it over to leadership and they can use it as a clear case of work being done. A quick failure is also ok as long as there is learning from it and how do you know if there was learning if there is nothing in the end?

Tooling

Does tooling matter? Well, someone could argue that it doesn’t as long as it does the job, but I’m yet to find any tool that works as well as Google docs: it is accessible everywhere you log in, searchable, shareable, collaborative. Works well at work and works well for personal things. Even this blog post originated in a Google Doc. And, yes, I tried other tools.

Conclusion

Same as the introduction: do yourself a favor and document everything as if your activities and thoughts were relentlessly producing logs. Offload cognitive overhead to docs and make your brain busy with now.


No comments


Finding my Deep Work

September 15, 2024 Opinion No comments

This post is original content by Andriy Buday.

NOTE: I wanted to gather my thoughts on the topic of “deep work” before going through the book “Deep Work” which I just picked and started listening to.

When and where are you the most productive? Does it ever happen to you that in a few hyper-focused hours you can complete as much as in a few days of ordinary pace work? Do you think it is possible to make these hyper-focused hours happen regularly every day?

Shallow Work

In the past I could be really focused on simpler, somewhat repetitive work. I remember I once had to add some extra data to our database and pull it through all layers and get into the frontend. Typically in that project this would take a week or so, but because I did this so many times one evening of hyper-focused work was enough and the PM who requested this was super surprised “you are very quick” with big eyes. Occasionally this looked like I was an overly competitive person. I remember at my first job I got an assignment to create some medical forms. I was maybe 2-3x faster in creating them compared to a more tenured person. I didn’t compete, it was just focused and fun work to me. This type of work is something you can grind through if you have a looming deadline.

Deep Work

But what about the work when more deeper thinking is required? It’s normally harder or next to impossible to bluntly grind through. It’s different in a way that any distraction derails the train of thought. Imagine, you are writing a design document, and you need a bit of extra info, so you search for that info, and a few dozen browser tabs away you realize you no longer remember what you were looking for and what you are doing on this particular page and that now it’s time for your meeting on another topic. I see deep work as periods of intense uninterrupted focus when I can make major progress on something hard to do.

Ideal span of focused time

For me ideal stretches of focused time are always longer than 30min and shorter than 3 hours. I found that getting into the deep work requires “warming up”, pretty much like in sport activities. After that, maintaining intensity is easier but never lasts longer than 4 hours, after which productivity goes down rapidly.

Mental capacity

There is limited mental capacity available on any day for deep work. I imagine it as a capped reservoir. The only way to have it full is to be well rested (proper sleep night before, healthy body and mind). Working in focused mode is like directing the flow to harvest energy on what you need. Distractions are like huge leaks that take time to fix. The reservoir is very hard to expand, but you can train to make use of the flow much faster without the lag time, so instead of requiring 30 min to get into the focus you might train to shorten this time.

Environment

Another aspect of focused work for me is the surrounding environment. I am working on creating routines. Say, to write blog posts I decided to do them in a bubble tea place each time after dropping off my kids for karate classes. I know I have an hour of active work and there will be very little time during the week to get most of it done, and then one more stretch of work early on Saturday or Sunday morning. This post is written in three one hour sittings.

Distractions

Going through social media feeds on mobile phones is an obvious time and attention killer. But even something that is more important and you have to do has detrimental effects. For instance, just 4-5 meetings are normally enough to exhaust mental capacity for any deep work on that day, especially if they are spread throughout the day. Or, say, replying to messages from your boss is something important, but again if it comes in the middle of your deep work on, say, writing an important doc you lose your attention and will have to get into the flow of writing again. Small things often go a long way to reduce distractions, things like putting the phone away, having a clean work desk, using full screen mode, etc, whatever works for you.

Time of the day

A “cheat code” appears to get those 3 hours of work before any meetings. I know it is a cliche to say “wake up at 5AM and get most work done before others wake up”. I found this to be true, except it doesn’t work for me mainly because at 5AM I’m a zombie and not a human (maybe if I was a robot it would have worked ;) ). This works though if I go to bed at 9PM, which is super difficult as even my kids laugh at me when I mention going to bed this early.

Commitments

I mentioned deadlines at the beginning and I think they are a very important motivating aspect for actually getting into the deep work. A caveat that comes with deadlines is that often they are perceived as something far in the future so we tend to procrastinate until its too late. Thus, something that works better are shorter cycles. For me, weekly cadence seems to be the best, both in my personal life and at work. For projects that I drive at work I usually establish a weekly cadence of planning/commitments. I have written about setting up challenges with friends and I’ve been doing this in one or the other form since 2016.

Key contributors to focused work for me:

  • Plenty of sleep the night before
  • Distraction-less surrounding environment
  • Very early hours (or very late hours)
  • Dedicated spaces for specific types of work
  • Having a goal for each session
  • Commitment of some sort (work deadlines, self-goals, promises)


No comments


Is Being a Generalist Software Engineer a Good Thing?

September 7, 2024 Career, Opinion, Success, Uncategorized No comments

It probably doesn’t compile otherwise why be so unhappy?

Somehow I became a generalist software engineer with a diverse domain experience. I started career with C# and moved to Javascript and then to Java and now C++. I worked for healthcare, online entertainment, nuclear energy, e-commerce, and advertising industries. In this blog post I want to share some of the details of these experiences and conclude on whether being a generalist is better than being a niche engineer.

Technology Lens

The very first program I ever wrote was in QuickBasic in grade 6 (1999). The school computer I wrote this was only capable of running some version of DOS. Computers at university ran Windows and I learned to code in C/C++/C# + some more obscure languages (Prolog, Algol, Pascal). In my first job I wrote desktop and mobile solutions using MS technologies, mostly written in C# with WPF & WCF. My next gig was all about performant backend services with a mixed technology stack backing a multi-million user website. At my next job I found myself translating nuclear material accounting code from the 70/80s written in PL/I that ran on mainframe into Javascript or C#. Most engineers who wrote the original PL/I code either retired or died. This job taught me that I can love a dynamic programming language. Then I moved to work for Amazon, it was all about launching new business workflows and scaling it with Java services backed by AWS and ReactJS frontend. Now at Google I mainly write in C++, but from another perspective for me there was a big shift from working on products towards working on infrastructure that supports traffic for billions of users.

Domain Lens

Now I want to have a look at all of the same jobs but from a different perspective. The first projects I worked on were for healthcare providers. Honestly, I didn’t give myself much thought about the morbidity of the things, the fact that much of the software was for hospices didn’t bother me as I was operating on the level of tasks. It was only later when I was working on a mobile app for nurses to visit patients at their homes did I internalize what this all was for. Next job probably wasn’t that noble – it was in online entertainment, more specifically sports betting. I even had an account with a competitor and placed small bets on sport events to understand how they do things compared to us. Saving the world from making more atomic bombs? Yep – that was my next job, kind of. On the ground what I was doing was merely software for IAEA (UN) and its agents who went to nuclear facilities and collected nuclear material data, performed different checks and recorded them in the app for later analysis. I got a chance to visit a nuclear reactor and learn how it works. Next gig was about enabling small companies to sell more stuff at Amazon. This was about enabling an entire channel of dropshipping for the India marketplace: loading inventory into Amazon systems, processing customer orders, invoicing, etc. This allowed me to have a good view on how e-commerce works. These days I work on supporting online advertisement from inside by working on infrastructure and tooling that allows other engineers at Google to deliver solutions to show you relevant Ads. I know ads may sound like a bad thing, but the free internet exists thanks to ads. Ads pay for those transatlantic underwater internet cables and all the other things that power today’s internet.

Cultural Lens

All of the companies I worked for were very different culturally. First job was a very homogeneous environment, all of us were Ukrainians, fairly young and we worked for our American customers who on their side were also culturally similar among themselves. I think communication gaps existed due to time zone differences and English language skills on our side. Next job was maybe half Austrians and another half of East europeans. The product we worked on was our own so I think we cared about its success a lot. I am actually not sure if I fit into this environment culturally, but I thrived on the technical front and delivering results. At the same time this was when I made many new friends who remain friends until now and I even stayed at their home on my recent trip to Europe. The United Nations is definitely a culturally most unusual environment I had to work in, mainly because of the diversity of nationalities and backgrounds. Any day at the UN premises there were people from over 100 different countries, my team alone had people from all of the continents. Something that was a bit less diverse was age, as many of the people who work for the UN are accomplished individuals with some years behind their backs. This was the place of internalizing that not everybody has the same life views on it and it’s all ok. It was extremely fascinating to learn from my colleagues. I would say that on a macro level both Amazon and Google are culturally similar – we are ambitious technically savvy individuals striving to make an impact. Though on another level Amazon is a fast paced, high intensity, customer centric, and deadline driven company whereis Google is more mission driven, long-term oriented, with more emphasis on innovation.

Conclusion

I can probably wear many other lenses to look at my past experiences, such as, Impact, Scale, Learning, Personal Fulfillment, WLB, Collaboration, Communication, etc. But even with the 3 lenses above it is clear that the diversity of technologies, domains, and cultures pushed me to become a generalist software engineer. Arguably, this isn’t necessarily a good thing, being extremely deep into one technology and domain can land you a ludicrously high paying job. I saw people sticking around and climbing corporate ladder rapidly, something that I couldn’t do with all the switched I did, and at the same time I saw directors being laid off just because there is no need for their role any longer. In today’s economies of scale the winner takes all. If you are at the right place and time and win the game – it is all yours. On the other hand, if you are not that “winner”, adaptability gives you an advantage of switching when needed and grabbing at least some piece of the pie or, maybe, a chance to win another game next time. I don’t know what is right, the above was my journey and it continues. What are your thoughts on going broad vs deep in your software engineering career?


No comments


From Fish Tanks to OKRs: Measuring Impact

September 1, 2024 Opinion, Success No comments

“They reproduce – that’s how you know!”

Office Fish Tanks

During one of my business trips, I had an interesting encounter with a person responsible for maintenance of the fish tanks in the office. As we chatted about his work, he shared an insightful moment. His employer wanted to measure the results of his work and had once asked him, “How do we know you’re doing a good job?” He pointed to the fish tank and proudly said: “See those little fish? Fish in this tank reproduce in captivity and that’s how you know I’m doing a great job.”

In this post I would like to go over my experiences with measuring success and work results in the context of different jobs I had. I want to highlight some personal learnings from each of these experiences.

Experiences

In my first role I didn’t care about the business metrics or showing the results of my work, I was a grinding machine – I had a job and I had it done. Did my management care about the work I did? I bet they did, otherwise they wouldn’t put me through two promos. With my first experiences of leading a team I started looking at things like tasks completed, sprint burndowns, etc. In retrospect I was very focused on tracking “work completion” for myself and my team that I might have overlooked connecting this work to actual business impact. I was lucky someone did this for me and our work delivered results but if I was there now I would have spent more time understanding the business.

At my next job, my team owned multiple backend services where performance metrics were critical. “We need to handle 7TPS on a single node, how many nodes do we need to handle the entire traffic?” “This API is slow and has weird behavior of being very slow for some of the requests. Can we figure out the bottleneck and get P99 of requests <150ms?” I think this was the job when I truly understood how technical solutions connect to business success. I found the performance bottleneck and this allowed for a “bet from autocomplete” feature launch which improved user engagement by xx%. (Btw, the bottleneck was a forceful garbage collection as a way of reducing memory, instead I got rid of this memory optimization and instead asked for more memory on servers hosting the service).

Things were somewhat strange at my next job. At first I worked on an app for IAEA agents to use to record their activities during their visits to nuclear facilities around the world. I didn’t know exactly how they measured their success even though I was curious. But later I had a chance to work on a scientific/statistical tool that would take raw nuclear material accounting data and perform all kinds of analysis of the data, come up with reports and KPIs. In a way this was a measurement product by itself.

Amazon is famous for being data driven and measuring everything. When I worked there everything had to be backed by data. And this wasn’t just for engineers. Same standard applied throughout the entire company. My promo had to be backed by the list of all the projects I completed, impact they had, stats on code, etc, etc. Dates mattered a lot as well. Market is ruthless and requires things to be completed before the deadline (think Prime Day, Re:Invent).

Google is another example of an extremely data driven company and I have had a chance to work on things related to how Google makes decisions based on data. Effect of any smallest change is measured on a small percentage of traffic in order to make an informed decision. There is an experiment almost behind any code change. Google taught me to always add a section “Landed Impact” at the end of every design doc and then populate it post launching the document with specific realized impact. Google had so much impact on my life that I’m setting my personal goals using OKR methodology. If you want some related reading, consider reading the book “Measure what matters”.

Conclusion

Understanding the success of a project is about aligning technical results with business outcomes. For example, if you’re optimizing code for faster processing, link this improvement to reduced server costs or increase in revenue, and then measure all of these components. And from a career perspective, you always want to be able to say what you did and what impact it had. The impact has to be stated in numbers and should have some meaning behind it. People should care about your numbers. If no one cares about your numbers, think again if what you are doing is worth doing.


No comments


Consistency is Hard: connect periods of inspiration to achieve durable consistency

August 24, 2024 Opinion, Success No comments

This is original content by Andriy Buday.

Rock climbing a high mountain consists of connecting multiple single pitch climbs, thus called “multi-pitching”. This is me on Stawamus Chief mountain in Squamish, BC, Canada.

Inspiration doesn’t last

One of my observations both in myself and in others is that being consistent is hard, especially in starting something new or in high effort activities. Think about when you get inspired to go to the gym every other day only to discover it is hard to find time, or think about when people talk about yet another self-help book that promises success if you just follow some simple morning ritual and “x rules of success” only to realize following those rules is unrealistic, or think about someone who fell in love and puts effort into looking and behaving exemplary only to revert to the baseline after some time.

Arguably, it is in human nature to have waves of inspiration, attempting something, and abandoning it if it doesn’t pay off instantly or after it has paid off. Lack of time, competing priorities, procrastination, laziness, waiting for a better time, just not feeling like it.

In this post I would like to document for myself and to share some of the instances of things that worked for me and didn’t work for me. I will try to analyze my own behavior to see if any of this can be generalized and if there is a way to figure out a way to make things work.

Consistency fading away

Let’s start with some scenarios where I had success but then consistency faded away in a very long run:

  • Consistent blog post writing
    • I have 328 blog posts over here. The majority of posts are old ones from 2010-2013 with a monthly average of 5-10 posts.
    • Inspiration: blogging was popular around 2010 (no gen AI, no insta, not much of twitter) and it paid off in terms of people getting to know me, building connections. I would have not done well in my career without this blog.
    • Reason for less blogging? I no longer feel that the benefits justify effort, anyone can use Gen AI to create a blog post a lot better than this one diminishing my enthusiasm, no one really reads posts these days, internet is just over-saturated. And frankly “I got tired” as was put by one of my early role model, Scott Hanselman, after 20 years of blogging.
    • Conclusion: blogging helped me in the past; it can be useful even now to organize my thoughts in an environment outside of work, but does it pay off?
  • Reading books
    • I don’t know the number of books I read, but I had multiple annual goals of reading, say 24 books a year, 6 tech books, or 13 investment books, etc. and I succeeded in many of those annual goals or had partial success (hard to do a book every 2 weeks).
    • Inspiration: eagerness to apply knowledge to advance in life, bright eyes thinking that books have all the answers, falsely thinking that book authors are another breed.
    • So I don’t read books now? Well, I do, but a lot less. Over time to me many books became repetitive and boring, especially, if they are on the same topic (say, productivity) plus it becomes annoying to spend time listening to non-original content and authors citing all the same research over and over. Another issue I have is that I don’t have a proper mechanism for remembering things, so often it is wasted time. You read a book and a week later you have a hard time recalling what was there.
    • Conclusion: no doubt reading books is beneficial, everyone should do it, but is it so hard to continue to find inspiration, time, and satisfaction in reading them.

Cyclic consistency

Now let’s look at some of the cyclic scenarios when I returned to the old consistency for some periods of time:

  • Interview prep
    • Arguably one would say that everybody prepares for interviews when they change jobs, but I went through a few instances when I was preparing for half a year or so without any interviews lined up or even thoughts of changing jobs. Yeah, just doing some 5-10 leetcode every week for fun.
    • Motivation: sense of importance of advance preparation and always being ready, but also I just like coding a tiny bit of something and feeling completeness.
    • Conclusion: cyclic approach worked great for me in the past, but after multiple months it becomes less fun I start to question my sanity.
  • Waking up in the morning
    • I’m likely an evening person (if there is such a thing). I had many periods of being an early morning person. You know “new you” waking at a crazy morning, “deep work”, and all of that, but it doesn’t always work like that, very often I feel like a zombie and after multiple “zombie” periods I gave up on the morning thing. Ironically, I started this blog post 6:30AM and am almost done by 9AM.
    • Inspiration: there is like a barrage of books, articles, gurus, whatever telling that if you claim morning to yourself you will have done more till noon than most people in a week. Lol, I wish that was true.
    • This one is painful. I had so many failures after attempting this that. Something that also bothers me is that I was extremely productive at some of my previous jobs when I would come to the office like 11:30AM after barely waking at 10:30AM but then would work till very late.

Consistency on the raise

And now I want to examine two cases where I consistently improve consistency if that makes sense.

  • Physical exercises
    • One of the things I did not pay attention to in childhood and early adulthood was health and physical exercising. I was healthy for the most part, I didn’t care how I looked. In 2016 I started having periods of running, then I discovered rock climbing, and in 2021 I went nuts and worked out 365 days, including 148 rock climbing gym visits (my climbing stuff), 78 runs, 87 hours of weight training, and many other activities.
    • Inspiration: this came naturally, originally motivation was establishing challenges with friends, later I found it could be fun to beat personal records and socialize in a bouldering gym, a also noticed how it helped dealing with mental stress and my back pains are gone.
    • Conclusion: consistent payoff and little downside made this ever more consistent activity. I might not hit 366 days this year, but will be very close to it.
  • Financial goals
    • As a disclaimer, I work for FAANG company but I work in Canada and started fairly late, so I’m not one of those multi-million net worth guys advising on life. Instead, while making regular (still high) software engineer money in Europe, I’ve been very consistent and deliberate in management of money. I have a custom spreadsheet I update every month since 2012. I read multiple books, tried a bit of more active trading and switched to super-simple strategies. All-in-all just grinding a consistent approach to money. Not that I didn’t make mistakes, purely from financial perspective I should have moved to the US, I bought a townhouse in Vancouver at the worst time possible and some other mistakes.
    • Inspiration: I guess sense of security and thoughts about the future are a great driving factor, but a lot of actual inspiration came from reading popular financial books, like those about Warren Buffett.

Conclusion

It is great to get inspired and I recommend deliberately looking for sources of inspiration: read books, look for mentors, create plans for yourself. With that having said, inspiration lacks durability and this is where work to build and maintain habits starts, it is hard and often results in failure. In my experience, starting something and then failing is OK as long as you start the cycle again and again, pushing the time of a failure further and further away in any given cycle. It is critical to ensure that your cycles are the right ones (another topic), but eventually your cycles will connect into one uninterrupted wavy line that takes you to your goals. Don’t give up!


No comments


Quick thoughts on Conflict Resolution Styles

February 12, 2024 Leadership, Opinion No comments

Hopefully a short post. As always opinions are mine.

I always figured dealing with conflict was something you just…did. You know, no need for fancy theories or structured approaches. Recently I was asked what my conflict resolution style is and how it matches to style of other people. So I did a bit of research, I mean, in a lazy way:


Andriy: > Give brief list of conflict resolution styles as bullet points:
Gemini: > Absolutely! Here’s a brief list of the most common conflict resolution styles:

  • Accommodating: Prioritizing the needs of others over your own and seeking to maintain harmony.
  • Avoiding: Sidestepping or postponing dealing with the conflict.
  • Compromising: Finding a middle ground; each party gives up something to find a solution.
  • Competing: Focused on winning and advancing your own needs above all else.
  • Collaborating: Working together to find a solution that fully satisfies everyone’s needs as much as possible.

Andriy: > What’s the origin of these conflict resolution styles?
Gemini: > The primary origin of the framework for these conflict resolution styles comes from the work of Kenneth Thomas and Ralph Kilmann in the 1970s.


Ok. That kind of makes sense and I have a hunch I have read about those at some point in my life. Now I have an exercise for you, which I’m doing myself along the way as well. I promise it will get more interesting:

  • Determine your own conflict resolution style by either taking a quiz online or by just thinking through those. I’m kind of combination of Collaborating, Compromizing, and a bit of Competing with complete intolerance to Avoiding style.
  • Now try to determine the styles of people you have to deal with, say collegues at work or people in your personal life. For myself, I created kind of a map of few of the stakeholders at work.
  • Now try to think of pros and cons of each of the styles and how they might impact you, other person, or what would be the best situation to use a style. Yeah, internet has lots of these, and I generated some stuff below, but it is more interesting to think about this while having context of yourself or others you know. Think of maybe 2-3 people, not to overwhelm yourself.
  • Now the fun part: mix and match yourself to these people and recall how your interactions where with them. For myself I found that:
    • We spend to much time in “analysis-paralysis” when another person is collaborating as much as I am.
    • There is a lot more compromizing on my side when dealing with a competing or avoiding person, which is probably detremental for me and leaves a bit of resentment.
    • Things get solved very quickly with an accomodating person, but then do I lose some of my credit with them just because they haven’t spoken?
    • … and many more…

Andriy: > Add one pro, one con, and one recommendation under each conflict resolution style bullet point.
Gemini: > Absolutely! Here’s the list expanded with a pro, con, and recommendation for each style:

  • Accommodating:
    • Pro: Maintains relationships and reduces tension.
    • Con: Can lead to neglecting your own needs.
    • Recommendation: Use strategically in low-stakes situations or when preserving harmony is crucial.
  • Avoiding:
    • Pro: Allows time to cool down and gather your thoughts.
    • Con: Doesn’t actually resolve the conflict, which can build resentment.
    • Recommendation: Employ only as a temporary measure, ensuring you return to address the issue later.
  • Compromising:
    • Pro: Can lead to finding a quick and somewhat fair solution.
    • Con: May limit creativity and not fully address everyone’s concerns.
    • Recommendation: Best when finding a temporary fix or when issues are of moderate importance.
  • Competing:
    • Pro: Can be useful when immediate, decisive action is needed.
    • Con: Damages relationships and may not lead to the best long-term solution.
    • Recommendation: Reserve for emergencies or when power dynamics are heavily imbalanced.
  • Collaborating:
    • Pro: Leads to solutions that genuinely satisfy everyone involved.
    • Con: Can be time-consuming and requires everyone to be fully invested.
    • Recommendation: Aim for this style whenever possible, especially for high-stakes conflicts or building deep trust.

This self-invented exercise helped me realize I need to be more mindful of the situation when handling conflict. I should explore styles that feel less natural, like strategically using avoidance when emotions are high – as long as I remember to revisit the issue later or that occasionally I need to compromize less in favor of achieveing better quality.

What are your thoughts?


No comments