Want to Make Meetings
Unboring?

If there's one thing in every tech person's mind, it's how to avoid all those unproductive meetings. But there's a way out, where we do more and talk less.

What's Inside the Book?

In just 37 minutes, find out how to be exceptional:

  1. The valuable quality that founders seek in engineers, but never talk about.
    A phone call from my CEO, wherein to my thought process he said, "if you can just find more people who think like this!" What did he say, and why is it important that you know it?
  2. The one thing exceptional engineers never complain about, guaranteeing their growth.
    Your starting point decides how good you're at your job. Here's how CTOs expect you to be part of the solution rather than the problem.
  3. The speech pattern of successful engineers that CEOs love to pay a premium for.
  4. What algorithms teach you about salary negotiations.
  5. The only outcome that exceptional engineers provide, which average ones always miss.
  6. The import thing that smart engineers love, but average ones hate with contempt.
  7. Why exceptional engineers never really "work" in the office.
  8. Why the highly paid don't join "good companies."

About the Author

Hey! I'm Raahul, and I love technology and teaching.

I started programming at the age of 11, sold software when in college, and have always held senior and leadership positions in major SaaS startups. At present, I'm innovating the next-gen AI-driven analytics engine at WebEngage, along with architecting high-scalable features that handle load in the tens of millions.

I specialize in software architecture, algorithms, and artificial intelligence. I have a Master's in Computer Science, specializing in Machine Learning, from Georgia Tech. I build deep-tech differentiators that grow profit and retention.

I've been featured in the following mainstream publications, events, and organizations:

Why "The Value Artisan?"

I've always focused on the technical aspects of projects. Yet, the one genuine complaint founders have had with me, "you don't mentor people enough!" It's not enough to chart new territory, you also have to help others get there.

I've taken that to heart, and have decided to put in a significant amount of time mentoring engineers, and helping them weave magic using 1s and 0s. Till now, the only source of mentorship has been if you work directly with me. I don't even get time to mentor people not directly in my team, because there's always a lot going on.

But as a self-learnt programmer, there have been a lot of things that I've learnt, which the internet today just doesn't teach. Websites teach you what is convenient to be taught, not what is important to be learnt. You can only learn effectively from people who have walked the walk. Most of my friends who are at the pinnacle of technological innovation just don't have the time to educate. And most who have the time to educate have not achieved anything special.

Moreover, most of my hundreds of design documents, decision matrices, source code, are hidden behind the proprietary walls of the companies that I've worked for. None of those are accessible for learning to the outside world, although they all can benefit from it.

This is my way of contributing back to the ecosystem at large.