When I, a software developer, connected with the environment

My romance with Kando began about 3 years ago when I was a freelancer. I met with Kando and was tasked to develop a basic information system. One thing led to another, and by the end of the first stage of the project, more and more development requirements were coming in, and multiple monitoring and analytical capabilities were being added to the system. At this stage, my level of involvement in the company had grown significantly. I had begun to meet more and more people from Kando, and this is the point at which I began to absorb and understand the company’s atmosphere and rhythm.

But, to understand where I was coming from on meeting Kando, I’ll briefly share my background.

Over the years, before becoming a freelancer, I worked in a wide variety of software companies of all types and sizes, from small/medium-sized startups to giant corporations with over 10,000 employees. The common denominator among all the companies I worked in was that the products I was part of developing were geared to a clientele of primarily large enterprises. Usually, the development cycle, sales and deployment of these products was very long, so the time lapse from the day we bought a new product to market to the day it arrived alive and kicking in the hands of the customer, could be over a year.

Conversely, at Kando, the interlude from the moment requirements are received to the moment when the solution exists and is delivered to customers is incredibly short, and this definitely gave an adrenaline shot to my motivation level.

Aside from seeing that the products I develop in Kando reach customers immediately, knowing that the products have a hand in directly and almost instantly improving the environment, have helped me a great deal to connect with the company and feel that I also make a contribution.

As time went by, my ties with Kando grew closer, I met amazing people, who exhibited professionalism and concern for the environment. The Kando team genuinely feel a sense of mission in promoting environmental improvement. On the professional level, Kando people are the best in their field! It is enough for them to see or even just to smell the sewage to know if there’s pollution in the wastewater. They simply live it every day and their knowledge of the subject is astounding.

Apart from their professionalism, the people at Kando are exceptional on a personal level. The first thing that stands out when entering Kando’s offices is the informal and relaxed atmosphere in the office. Everyone treats each other on equal terms. The CEO, Ari Goldfarb, is available to every employee and his door is always open (in fact, Ari has no room of his own and he sits with everyone in the open space).

One day, one of the employees decided he wanted to grow vegetables in the yard adjacent to the office. During the four o’clock coffee break, he enlisted three more workers, within a moment, there were hoes flying in the air and an hour later, there was a magnificent vegetable garden.

A month later, the vegetables were already part of the shared salad that was cut and eaten by everyone.

As time passed I felt how drawn I was to this project, how connected with the people and the spirit of the company and how the product I was developing with the Kando team had become my “baby”. When the conditions ripened, my transition to being a Kando employee was smooth and natural.

The immediate professional challenges I faced once I entered the company were to introduce proper work methodologies for a software development environment, to choose the appropriate management tools, and to instill the importance of implementing each stage of the development process in a non-development company.

We chose to work with the agile methodology (scrum). Everyone got on board immediately and were thirsty for more information on the subject. The importance of QA in the software development process has also been internalized and it is now possible to state unequivocally that the Kando team understands the development process and the importance of each stage.

The agile methodology generates short development cycles (two weeks), at the end of which we have another capability, which two weeks ago did not exist. With Kando’s professionalism in the sewage field and our work with Agile we are unstoppable!

So what awaits us in the future?

Our future development list is loaded with innovative software and hardware ideas, our next generation of self-activating smart units is in the advanced stages of development, and there is no end to the new ideas from the field. In short, there’s plenty to look forward to.

* Agile – https://en.wikipedia.org/wiki/Agile_software_development

* Scrum – https://en.wikipedia.org/wiki/Scrum_(software_development)

* QA (Quality Assurance) – https://en.wikipedia.org/wiki/Quality_assurance