loading...
JFrog

VP Of Technology At JFrog

greenido profile image Ido Green Originally published at greenido.wordpress.com on ・2 min read

At last SwampUP, I had the opportunity to talk with Alan Shimel, Founder and Editor at DevOps.com. We covered what I do at JFrog and spoke about the definition of the role “VP of Technology”. We also covered some interesting new products we offering these days to help developers move faster.

I told Alan that I define the role as “finding leverage points in (JFrog) technology to support the business”.

I am passionate about helping developers and with this role, it’s all about bring “extra” value. When you want developers to be more productive and effective you should help them with practical use cases and new ways to use tools/services. The main motivation is to make their software development process flow faster and in a more secure way.

This is what we try to do at JFrog. We are taking the insights from our 5,000 customers, per vertical and industry and driving best practices that are more suitable to these type of companies. Take for example the financial industry, the needs and requirements are similar in many organization and we see a method that works well. This is empowering us to suggest these lessons to others with data that support it. It’s not only an academic best practice but a real-world example that works in certain parameters and constraints.

This guided us to the last acquisition of Shippable. We wanted to offer developers a better way to manage their continuous integration / continuous delivery pipelines.

I hope that JFrog pipelines will be in GA soon. So far, the Beta customers are quite happy with the added value that they are getting out of it.

pipelines at sunset

Happy Wednesday!

Posted on by:

greenido profile

Ido Green

@greenido

Ido Green is an entrepreneur that loves to build companies and help developers. More: https://ido-green.appspot.com/

JFrog

JFrog products seamlessly integrate with practically any development environment on Earth, from legacy code to the most recent containers and micro-services.

Discussion

markdown guide