Don’t cross the Rubicon: engineering practices you don’t want to delay

Back in 49 BC, Julius Caesar broke an ancient law forbidding any general to enter Rome with the army by crossing the river Rubicon.

By doing so, he declared war and did something that could not be undone. Ever since, ‘crossing the Rubicon’ has come to symbolize the point of no return.

As a tech leader at ThoughtWorks, a large part of my job involves recommending practices to our clients so they can build and deliver good quality software, faster. In doing so many times for many clients, I have created a toolkit that contains practical advice that may help you avoid the point of no return.

Join LeadDev.com for free to access this content