Remove Continuous Delivery Remove DevOps Remove Microservices Remove Test-Driven Development
article thumbnail

Talks with Software Development Experts Initiative Part 2

Apiumhub

Viktor Farcic We also had the great opportunity to interview Viktor Farcic, a Developer Advocate at Upbound, host of DevOps Toolkit, and cohost of the podcast DevOps Paradox. Viktor starts his interview by telling us a bit about how he began his journey in this industry and his passion for continuous delivery.

article thumbnail

Continuous deployment without downtime

CircleCI

As engineering teams increasingly adopt DevOps as their software development strategy, they are becoming faster and more efficient. Unfortunately, this speed and efficiency can expose cracks in the delivery system as well as other bottlenecks to productivity. This requires both CI and continuous delivery.

Insiders

Sign Up for our Newsletter

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

article thumbnail

170+ live online training courses opened for March and April

O'Reilly Media - Ideas

Get hands-on training in machine learning, microservices, blockchain, Python, Java, and many other topics. Advanced TDD (Test-Driven Development) , March 15. Java Testing with Mockito and the Hamcrest Matchers , March 19. Microservice Collaboration , March 7. Architecture for Continuous Delivery , March 25.

article thumbnail

15 Books by leading software architects

Apiumhub

DevOps: A Software Architect’s Perspective ” by Len Bass, Ingo Weber, Liming Zhu . DevOps promises to accelerate the release of new software features and improve monitoring of systems in production, but its crucial implications for software architects and architecture are often ignored.

article thumbnail

Lean Software Development: The Backstory

LeanEssays

To counter sequential processes and the long integration and defect removal phase, agile software development practices focused on fast feedback cycles in these areas: Test-driven development: Start by writing tests (think of them as executable specifications) and then write the code to pass the tests.