Guy leads Vim’s Enablement squad in Tel Aviv. 


How does your team decide if you should reuse code?

With software, we are not trying to invent the wheel. We will always use off the shelf products when we can – commercial or noncommercial instead of reinventing them. Same with code – All of our Tech stacks rely on open source technologies (which is the best kind of code to reuse).

Our platform supports many customers and around our React client code, we try to design customizable applications to maximize reuse by dividing functionality into useful components.

On our Backend, we are wrapping reusable logic into micro-services that can be deployed and operated separately from the rest of the systems and applications.

As the examples above show, our base foundations rely on code reuse, but in a balanced way.

In our development culture, code reuse is not a worthwhile goal. Avoiding duplication is a worthwhile goal. Avoiding waste is a worthwhile goal. And you do both of these things by looking out for and eliminating repetition of your labor and of functionality in code.  Usually, our team will write the code we need, right up to the point that we start repetitively solving the same problem. Then refactor that solution out into a commonplace and refer to it.  When you do this, you’re not reusing code — you’re reusing valuable functionality.


What development language do you enjoy the most and why?

It really depends on the task. I love javaScript for quick POC and dynamic areas of the system, but I’d use C# for places I care more about architecture and code structure, and Python is always handy for the staff in between and number crunching.


You have traveled a lot; where has been the most interesting place you have visited and why?

I only traveled East-Asia, and India was fascinating. I love being able to talk to the locals. India is colorful, beautiful and ugly, very rough and real. After traveling there for 4 months, my Father (whose parents were born in India) came to visit me.

We went to search for his grandfather’s house in Kochi (south India) which they left at 1949, a year after Israel was established. The house was gone, but we were able to enter the empty Jewish synagogue and stand on the same floor where his Indian family was for generations.


What was the main reason you joined Vim?

After graduating from the AirForce, I looked for a team where I could continue to feel a  connection to my work. At Vim I found a home with a professional software development team at a startup that is working on meaningful real-world problems.


What three adjectives would you use to describe the Vim culture?

Friendly – Our R&D team is full of talented developers, who are motivated to create a great work environment, not just technically beautiful code.  We care about one another and spend time together outside of work.

Responsible – The data that is managed on our platform include Private Health Information from many patients.  It is our responsibility to build a secure architecture for separating peoples sensitive data and the rest of the business data.

Learning – Our business takes us into uncharted waters.  As a result, we are constantly confronting new domains and new technologies.  We eagerly jump into the unknown and learn as we go. We track gaps on the team and make sure to share knowledge by rotating developers through projects and pairing them with domain experts.


What is your spirit animal and why?

The wolf. As a child I was watching the JungleBook movie and noticed how the family pack grew, hunted and lived together. I like their commitment to love and family.

The power of the wolf brings forth instinct, intelligence, an appetite for freedom, and awareness of the importance of social connections. Like wolves I feel the liberty as a lonely wolf whenever needed, While I feel confident to work in a pack enjoy a sense of community, leading or being lead.