Palo Alto Networks

OCTOBER 22, 2024

{{interview_audio_title}} 00:00 00:00 Volume Slider 10s 10s 10s 10s Seek Slider The genesis of cloud computing can be traced back to the 1960s concept of utility computing, but it came into its own with the launch of Amazon Web Services (AWS) in 2006.

Cloud 105

Cloud Artificial Inteligence Software Review Systems Review 105

James Shore

JANUARY 11, 2019

Dependency Injection Demystified - 22 Mar, 2006. Continuous Integration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuous integration. (Hosted by Martin Fowler.). A 25-dollar term for a 5-cent concept. The Art of Agile Development (Book) - 2008. The Agile how-to guide.

Test-Driven Development 60

Test-Driven Development Agile Continuous Integration Testing 60

James Shore

JANUARY 11, 2019

Dependency Injection Demystified - 22 Mar, 2006. Continuous Integration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuous integration. A 25-dollar term for a 5-cent concept. The Art of Agile Development (Book) - 2008. The Agile how-to guide.

Test-Driven Development 60

Test-Driven Development Agile Continuous Integration Testing 60

James Shore

APRIL 9, 2021

Refactoring Databases: Evolutionary Database Design [Ambler and Sadalage 2006] describes how. However, data migration can take a long time, which requires special deployment considerations, as described in “Continuous Deployment” on p.XX. 1 XXX replace with direct reference when Continuous Deployment is written. Prerequisites.

Software Review 78

Software Review Technical Review Systems Review Test-Driven Development 78

James Shore

JANUARY 10, 2025

They also love test-driven development, pairing, continuous integration, and evolutionary design. CIO Magazine, Sep 2006 One of my favorite stories about how this approach fails is the FBIs Virtual Case File system, because there was a US Senate investigation, and we have a lot of details about what happened.

Engineering 141

Engineering Software Review Weak Development Team Agile 141

James Shore

DECEMBER 4, 2020

1 See, for example, [Van Schooenderwoert 2006], [Mah 2006], and [Anderson 2006]. Programmers continuously integrate their code, which enables the team to release their software whenever it makes the most business sense. There’s no point in Agile for the sake of Agile. What will it take to achieve that success?

Agile 59

Agile Software Review Technical Review Weak Development Team 59

Apiumhub

MARCH 26, 2019

Until July 2006, he led the software architecture R&D at National ICT Australia (NICTA) in Sydney, Australia, and previously worked at CSIRO, IBM, Microsoft and in academia in Australia. Dave has a wide range of experience leading the development of complex software in teams, both large and small, in the UK and USA.

Software Review 44

Software Review Architecture Technical Review Software 44