My Customer wanted an automated way to refresh an application database to a known state, to be done by non-technical personnel. As a DBA I know a lot of scripting, can build some small web interfaces, but why bother when there are ready available tools, like Jenkins. Jenkins is mostly […]
Agile
Continuous Delivery and the Oracle database (III)
In this series of blogs about Continuous Delivery and the Oracle database, I describe how to automate deployments (installations). In the previous two Blogs I have described the tools and techniques used to create and install migration scripts. In this Blog I will describe the ‘(un)happy flow’ for a database […]
Continuous Delivery and the Oracle database (II)
In the previous Blog I have described how to implement CD for an Oracle database by using migration scripts. In this Blog I will describe how to create migration scripts (automagically). DML scripts This is the more simple case because you need them less often. There are various data compare […]
7 Agile Estimation Techniques – beyond Planning Poker
Many of the agile teams I know are using some form of planning poker for their agile estimation. Agile estimations with planning poker is sometimes just not working. Reasons for this can be: the estimation features are too large, the team is not inspired to poker 300 stories, there is not […]
Stap voor stap, telkens verder vooruit
Woensdagavond keek ik weer met verwondering naar Zembla. Laat ik vooropstellen dat ik een aantal uitspraken tendentieus vind en iets te eenvoudig voorgesteld. De boodschap is echter duidelijk: grote miljoenen euro-verslindende IT-projecten die uiteindelijk niets opleveren. Ontwikkelaars zonder feeling met de wereld van hun gebruikers. Complexe systemen waar een jaar […]
Continuous delivery culture. Why do we do the things we do the way we do them?
Usually at first there is a problem to be solved. A solution is conjured and implemented. After a while, the solution is re-used and re-used again. It changes depending on the person implementing it and his/hers background, ideas, motives, likes and dislikes. People start implementing the solution because other people […]
What is REST?
REST (Representational State Transfer) is a term often used in software engineering when talking about services or other API’s. A lot of these so-called RESTful services or interfaces are not RESTful at all. Even the author of REST gets frustrated by the common misuse; http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven: “I am getting frustrated by the number of people […]
Agile software development, the principles. Principle 11: The best architectures, requirements, and designs emerge from self-organizing teams.
This is the eleventh of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher […]
Agile software development, the principles. Principle 10: Simplicity -the art of maximizing the amount of work not done- is essential
This is the tenth of 12 posts about the principles of agile software development. Purpose is to go back to the start of the agile manifesto (http://agilemanifesto.org/principles.html) and discuss the implementation of the 12 principles in real life software engineering. Goals of agility are to go deliver software of higher […]