I have recently finished reading “Awareness: The Key to Living in Balance” by Osho. What can I say? It was not an easy one for me. If you are in search of harmony, the book might help you.

It might sound controversial, but try not to use your mind and analyze what you read. The book requires to be open to new ideas and to absorb the concepts.

As far as I understand, Osho did not write books. He mostly spoke and taught. So, this book is not the exception, and it is a written version of his conversations.


Of course, you have heard of the “never use GOTO statement” mantra, and of course, you are terrified not to follow the mantra. But why there is a lot of such statements in the linux kernel? Or why should you write as a few comments as possible?

What can we learn from the coding style of the project to which thousands of developers contributed?

If only the one thing I could extract from the linux kernel coding style, it would be the pragmatic approach to coding style. There is no one ideal and ubiquitous solution for everybody and every project.

The main title of the book “12 Rules” is not a good one. It sounds rather popular and unattractive. I believe many may pass by such a profound book, which may seem very superficial judging only by the title. The book is not that simple and requires a lot of mental work to understand its ideas.

If you have lost your bearings and are having trouble answering the question, “What’s happening to me?” then this book may be for you.

If you are lying to yourself and those around you or feel like you are losing control of your life…

While discussing a web application’s performance or request profiling results, it is vital to distinguish between the latency and the response time.

A simple formula to articulate the difference between response time and latency:

response time = latency + processing time

Response time is the total time it takes for the web service to respond to the sent request, including all networking latencies. Response time is the sum of processing time and encountered latencies.

Processing time is usually the time taken by the server from receiving the last byte of the request and returning the first byte of the response…

A trie is an effective data structure that could be an excellent addition to your problem-solving toolbox. Let’s see which areas the trie usage is more applicable than a standard set or map implementation. And what other benefits you can get from using it.

I like the name trie more than prefix tree or digital tree, although prefix tree is the most accurate definition. The name trie comes from retrieval but is pronounced as “try,” not “tree.” The idea was to distinguish the trie from the tree.

Try to guess what a trie is. I built trie from 4 words…

Are you going to run your first marathon? Learn from my experiments and why I run only 33.07 kilometers, not the entire distance — 42.2.

Before diving into the analysis, I state that I am delighted with the experiment. It is a colossal achievement, exceptional progress, and I never imagined that I can run such a long distance even if it is not a marathon distance yet. It is not a failure for me. It is an experiment with results. The results that I can use to improve myself and to progress further.


I do not think there should be…

I accepted the problem that I keep abandoning projects. There is nothing terrible in it, and I am a human-being with upsides and downsides. If you have an interest in why I have killed yet another project, keep reading.

I crafted a short answer that consists of two parts. The first one is that I have a psychological problem, the Sysphus scenario. And the second is that I tried to implement the idea that does not fit me well as a founder and eventually burned out.

Meet InboxQuery:

Before I deployed InboxQuery, I have around two months of productive work…

I found an interesting product created by two indie hackers — quickmetrics.

My first reaction was — wow! How brave are these guys?! If I were in their place with such an idea, I would research the market and google the competitors. And what would I see? That an ocean is red, many sharks eat each other and everything around them.

You have myriads of startups that work with metrics, and you have myriads of open source projects that solve the metrics problem.

I would be afraid a lot. I am sure that the folks did analyze the market and…

I have recently read a book about UI design, and I recommend it for developers who struggle to design approachable user interfaces.

If you are an experienced designer, the book is not for you. You probably won’t find anything new.

It does not have any water; it does not repeat itself and is structured well. It describes the basics and has many useful bits of advice that you can start applying right away.

It describes typography, colors, images, layouts, and other essential design concepts.

I recommend to read it and apply pieces of advice from it in practice. If you…

I was afraid that if I fail, I will not find a job because there will be a gap in a resume and many questions about what I was doing.

Photo by Gustavo Fring from Pexels

With that way of thinking, I drove myself into a dead end. I can’t keep working, and I want to do my projects. I have to keep working so that there are no holes in my resume, and I can find a job later.

That is a contradiction in pure form, and until you write it, you will not understand.

Today I think that…

Dmytro Krasun

I write about software engineering and my life journey.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store