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.

Latest Posts

James Clear says, "You're more likely to unlock a big leap in performance by trying differently than by trying harder. You might be able to work 10% harder, but a different approach might work 10x better. Remain focused on the core...
James Clear says, "You're more likely to unlock a big leap in performance by trying differently than by trying harder. You might be able to work 10% harder, but a different approach might work 10x better. Remain focused on the core...
Mediations Newsletter is becoming a curated newsletter where I will share what I've been thinking about recently and a few things passing from my screens, eyes, and life. The style will be between James Clear's 3-2-1, Cassidoo's...
How much time and money do we spend in our lives to make everything convenient? We optimized our lives so much that we had a lot of time to do many things. Yet, we lost the joy in them. Does everything have to be convenient? Some things...
The whole RFC process requires a blameless and trustful environment. If the organization operates with bad politics and secrecy, forget about RFCs. If an engineer doesn't trust others and doesn't believe people have good intentions, why...
Organizations should influence people to write RFCs, and the guides to writing them should be simple, clear, and concise. If an RFC template has ten sections that have to be filled, it ceases to help. An RFC template should be flexible....
If you publish an RFC and announce it only once, you practically fail. If there is one thing I learned in organizational leadership, it's this: if you want something, you have to repeat it. If you want to collect feedback for an RFC, you...
If everything is urgent, nothing is urgent. I see people share an RFC to collect feedback and tell the audience that they will close the RFC for comments in two days. If everything is urgent, how can people read an RFC while other urgent...
Not every RFC has to be shared with the whole company. Push RFCs to related people but be open to random people commenting on them. Related Note(s): 32b: Communicating Organizational Changes; 43: The Role and Responsibility of Software...
As the business decision has already been made, the RFC authors can decide which piece of feedback they will accept and which ones they will reject. If a team writes an RFC, they don't have to agree or accept every change request, but...
Similar to the business need we talked about above, the business decision has to be made before writing an RFC. RFC focuses on how, not what—deciding on what has to be done earlier. An RFC can't drive a business decision; however, it can...
All organizations have problems that everyone knows, but nobody has time to fix it. The time never comes to tackle those problems. Every product has other problems that need to be solved, features that need to be implemented, and changes...
Creating knowledge silos and building software in a team without involving others is unavoidable in growing organizations. That's why organizations create RFC processes to break down silos, collect feedback early and prevent impediments...
Many organizations adopt the Request for Comments (RFC) culture. Creating knowledge silos and building software in a team without involving others is unavoidable in organizations. That's why organizations create RFC processes to break...
If we ask a group of four software engineers what changes are needed in our system to improve its quality, we will get at least twenty ideas. When the RFCs are used to get support for any idea, it's a complete failure. This was one of...
Search Random