Διαχειριπη - reads as "diakheiripi".

Where it started?

For quite some time I've been interested in volleyball. One curious note - even though my parents tried to get me into sports and I attended several types of sports - nothing hit me. When I grew up and finished university only then I discovered volleyball and stuck to it. Who knows what would happen if I were offered to play it at ten years old age. Since then, I've been around Dnipro's Volleyball community for quite some time.

Back in autumn 2013 local volleyball community held second or third local Amateur Volleyball League edition. At that point, many things were done manually and took a lot of time. Fast forward to this day organizers have live streaming and coffee machine at the tournament site :) So I came up with an idea on how to automate this. Well, I was 23-old senior developer thinking I could do anything. As you might imagine, I've set myself up to a long journey. It's 2019 now, and I'm starting version 3. BTW version 2 started quite soon as a major rewrite after I realized how fragile I made that system.Another reason I've started it was that I was helping with my company's IT Academy - trying to teach people how to work in IT. As I'm not a fan of artificial programming tasks, like ToDo list, I had to come up with a real project idea. Which I did :)

So my "business" goals were:

1. Automate the process of managing tournaments. Scores, standings and game schedules in particular.

2. Provide a learning ground for IT academy students. Technology stack and the process should resemble the most common projects delivered by our company.

Why version 3?

Three years back, I've settled on a bunch of changes in my personal life. Between now and then I've moved to another city and two wonderful daughters were born with a 2-year split. As you might imagine, this project was not on my priority list, so it got very little attention.

Right now, I have a choice to revive the current project or start it from scratch. Given the number of things I learned professionally and the amount of work needed to change the current project to my vision, I believe it will be easier to start from scratch.

What Διαχειριπη means?

As experience showed me, indeed, two hardest software engineering problems are naming things and invalidating the cache. (I think we will get back to the topic of invalidating cache at some point in this blog.) As a good software developer, I chose the purely technical name "Volley Management." Well, it's for managing volleyball tournaments - it's the best one! Isn't it?) Back in 2013 I thought so. But times and times again, I doubted that decision.

So I think it is time to settle on a new name. I wanted to be creative, but my logical way of thinking had its part as well. I went fancy and turned to the Greek language - following the current technological trend in some commonly used tools like Kubernetes, Istio, etc.

First thing I translated Volley Management in greek and here is what I've got:

"volley"
"management"

So "management" is displayed by Google as "diacherisi". I was genuinely surprised that it's very close to my last name, "Diachenko". I think it is a good omen or wild luck :). Another piece to the name was that one of the translations for "volley" is "ripi" which is very similar to the ending "risi". I couldn't help myself to combine that.So Διαχειριπη it is!

A small note to the developers who will ever stumble upon it - I'm going to use it as a marketing name keeping VolleyManagement as a primary name in the code.

Next steps

To a readers surprise, I'm not here to talk about this project and its history. Rather it's future.

I plan to cover the design and development of this project from the perspective of a software engineer or architect. I want to capture my current way of thinking so I can get back to it for reference.

It is just a beginning :)