Remove 2004 Remove Agile Remove DevOps Remove Systems Review
article thumbnail

AoAD2 Chapter: DevOps (introduction)

James Shore

This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. To share your thoughts, join the AoAD2 open review mailing list. That continued even after I started practicing Agile. Fortunately, others in the Agile community weren’t so complacent. DevOps Sources.

DevOps 98
article thumbnail

Attending Oracle’s CodeOne? Here Are 15 Sessions Everyone Will Be Talking About

OverOps

We decided to focus on three main “categories” – Java, DevOps and Application Quality and Performance. All Things DevOps. DevOps and Agile Methodology: Lessons Learned [PRO3964]. DevOps Theory Versus Practice: A Song of Ice and TireFire [DEV5618]. Venkat Subramaniam , President, Agile Developer, Inc.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

AoAD2 Practice: Continuous Integration

James Shore

This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. To share your thoughts, join the AoAD2 open review mailing list. Continuous delivery is really just continuous integration applied to online systems. Beck 2004] (p. I discuss it in chapter “DevOps”.

article thumbnail

The Good and the Bad of Selenium Test Automation Tool

Altexsoft

And this tool is what we’re going to review today. With a list of several programming languages, all main operating systems and browsers supported, Selenium is currently used in production in such companies as Netflix, Google, HubSpot, Fitbit, and more. Integrated with Agile, DevOps, Continuous Delivery workflow.

article thumbnail

Grown-Up Lean

LeanEssays

I then make a sustained argument from the Linux experience for the proposition that “Given enough eyeballs, all bugs are shallow”, suggest productive analogies with other self-correcting systems of selfish agents, and conclude with some exploration of the implications of this insight for the future of software.