Candost's Blog

Candost's Blog

Candost

I used to think that reading would make me wise. One day, ten pages before finishing a book, I realized that I had read that same book before. At that point, my perspective on reading and, therefore, my life had changed. Now, I don’t care how many books I read; I take many notes, connect dots, and share what I’ve found on my blog and newsletter. I’m interested in many things at the same time (I’m a multipotentialite). On this blog, you’ll find me talking to about multiple aspects of life like leadership, software engineering, philosophy, psychology, software architecture & design, urban & industrial design, exercising, finance, Formula1 Racing, eating healthy, and many more. I’m a software engineering manager; that’s my current job. At home, I’m a writer and an avid reader. I rarely watch TV, movies or TV series. I don’t have any social media account (except Mastodon where I have automated posting of my new articles). Hence, I often miss the popular culture references in conversations. That’s alright. I don’t have FOMO; I embrace JOMO. I rarely read fictional books.

candost.blog
RSS

Latest Posts

People have different motivation drivers. However, when we form teams, they are motivated by team goals. Individual goals follow behind the team goals. Without an aim for the team to go, they cannot feel successful. No one wants to be in...
If you are joining a new team, one of the first things you should do is learn the goals of the team. If there is nothing, start by figuring out how you can create goals that are ambitious and can gather people around them as much as...
Specifying goals instead of methods creates confidence. When people try to focus on implementing methods to achieve a goal, they get stuck and forget the goal. Their focus only stays on the method implementation. When they focus on...
Writing up evaluations of 1, 3, and 5 years later and thinking ahead clears the mind and creates achievable goals. At the same time, these goals need to be measurable. We can't say "improve test results" as a goal. We need to define how...
Does this work with tasks at work, too? When people say that they don't have motivation, do they actually mean they need more clarity? Having a clear picture and unambiguous situations are more desirable at work. We look for more...
Strong product teams solve problems instead of focusing on delivering a product or a feature (a.k.a. output). Strong product leaders define the strategy and identify the problems for these teams. The strategy serves customers (not...
Being a consistent writer is one of the underrated and underestimated skills. If the writing and publishing are not in a rhythm, the success is very low. Most blog authors fail, not because they are bad at writing but because they are...
“You get what you repeat.” — Atomic Habits by James Clear Big-win moments are the results of previous actions. These previous actions can build up for a long time. Related Note(s): 24c: People need clarity, not motivation; Source(s):...
When we fail to form a new habit or get rid of a bad one, we focus on having motivation. But, what we need is clarity on the time and location of the habit. When we have vague dreams, it is easy to rationalize small excuses not to follow...
Don't slip away from your writing habit twice. It's better to do it every time, even if you can't make it perfect or as much as you want. Just writing a small piece is better than not writing at all. Don't fall into an all-or-nothing...
Committing to something is perceived as limiting your options, limiting your freedom of choice. But committing brings freedom. Freedom from things that don't matter. When there are many options for the same thing, we get stressed and...
Whenever we delay deploying minor fixes of software (changes in small batches), the repair cost also escalates. The minor work becomes major and requires more work every moment we delay. The increase in effort and expense is non-linear....
In large batch-size deployments, people become disconnected from the changes they made. Because there is a time gap between changes and deployments, they forget what they have fixed. And this might create new problems because if...
Big batch-size deployments lower the feedback cycle. With small batch deployments, we can get feedback early on in the product. With big batches, we wait for the deployment date. And if everything goes well, we start getting feedback....
When we have bigger-size deployments, the deployment team might seem like they own the changes. The teams who made the change can lack ownership. If the batch has a problem, who will send a hotfix? Source(s): Small batches for the...

April 2026

May 2026

Stats

729 posts published

Average 729.0 posts/month

Favorite day to publish: Saturday

Top words

  • mektup
  • software
  • team
  • teams
  • work
  • feedback
  • learning
  • engineering
  • building
  • review
Search Random