days
0
-39
0
hours
0
-6
minutes
-1
-1
seconds
-1
0
search

Claudio Pinkus

Claudio Pinkus
Claudio has nearly 40 years of experience in the creation and expansion of technology businesses, specifically in search, e-commerce and social media. He is a co-founder of NY-based CodeStream, Inc. Prior to that he co-founded Glip, acquired RingCentral, was CSO at Multiply, acquired by Naspers, and president/CSO at Ask Jeeves, acquired by IAC. Claudio is also an angel investor and advisor, assisting companies such as Zvents, acquired by eBay and Become, acquired by Connexity. He has founded and/or participated in the creation of over $2.3 billion in exits over the past 30 years. He attended UCLA, where he studied chemistry and computer science. CodeStream’s mission is to improve development team performance through communication, integration and transparency.

All Posts by this author

DevOps has been shifting left for years. Can your coding shift left, too?

How Far Left Can You Shift?

When you adopt a Shift Left approach, and developers start discussing code as they are writing it rather than once they are finished writing it, you can identify potential problems or approaches when changes are both possible and not very painful. What does it take to implement a Shift Left approach?

There's an easier way

Seven Advantages of In-IDE Code Reviews

When compared with code reviews using a Pull Request or a Merge Request as the primary driver of collaboration, In-IDE code reviews offer important advantages that result in higher author and reviewer satisfaction.

See why the Connected IDE is important for remote work

The Connected IDE: A communication-first approach drives collaboration (Part 2)

In Part 1 of this series we touched on the evolution of IDE from a personal, standalone tool to a connected and networked hub of all things code. We explained how connecting your IDE to your teammates’ simplifies communication and collaboration with two specific use cases: Discussing code in general, and performing code reviews right in your IDE, eliminating the context switching and improving knowledge sharing. In this post we will expand this to additional use cases and show how the Connected IDE is the most important step towards team collaboration in a world where we are all remote developers.

See why the Connected IDE is taking over

The Connected IDE is the gateway to increased developer collaboration (Part 1)

Like the standalone PCs of the 1980s, the personal IDE remains an island detached from the opportunity to improve collaboration for the development team and the company as a whole. A new era of connected IDEs is coming that does not require you to leave behind the IDE you love. Using modern plug-in technologies, your IDE can begin to evolve towards a truly Integrated Development Environment that will make collaboration easier while improving code quality.