Technology weblog

Certificate Python for Data Sciences

Posted at 10:11PM Sep 03, 2020 by Zeger Hendrikse in Python  |  Comments[0]

Trunk based development

The second way of DevOps states that we should aim for fast feedback loops. The more frequently we integrate, the faster we get feedback on whether our change works when it is integrated with the mainline. The more frequently we integrate, the smaller our batch size (containing changes), hence the sooner we can identify unexpected (integration) problems if any. As an ultimate goal, we aim to integrate continuously.

Creating a branch is doing exactly the opposite. It isolates your changes (from the mainline). The longer a feature branch lives, the longer the (integration) feedback loop becomes. This is exacerbated by the fact that integration problems become more difficult to trace down as the integration is postponed, as the batch size increases accordingly. Moreover, merges occur much less frequently (due to the isolation), hence merge conflicts are bulkier and thus significantly more difficult to resolve.

Concluding, it is good practice to merge your code back to the mainline (trunk) at least once a day. However, your final goal should be to commit dozens of small self-contained commits directly onto the mainline per day. A hallmark of a good developer is being able to split his work into many such small self-contained batches. It is a pivotal skill and the first thing junior developers should actually acquire! Therefore trunk-based development is especially recommended when there are (many) junior developers in the team! 

Posted at 10:47PM Jun 03, 2020 by Zeger Hendrikse in Continuous Delivery  |  Comments[0]

Technology and organisational capabilities for CD

In his presentation Continous Delivery and the Theory of Constraints, Steve Smith presented two slides on technology and organisational capabilities required for CD. The filed boxes merely indicate which capabilities he found to be present in some companies that he was working for.

Technology capabilities

Organisational capabilities

Posted at 11:31AM May 01, 2020 by Zeger Hendrikse in Continuous Delivery  |  Comments[0]

Rigorous SOLID leads to functional programming

If you take the SOLID principles to their extremes, you arrive at something that makes Functional Programming looks quite attractive: https://blog.ploeh.dk/2014/03/10/solid-the-next-step-is-functional/

Posted at 09:23AM May 01, 2020 by Zeger Hendrikse in General  |  Comments[0]

DevOps articles on TopTal

• Bridging Gaps: The Importance of DevOps Communication
• What The Hell Is DevOps?
• Getting Started with Docker: Simplifying DevOps
• 14 Essential DevOps Interview Questions
• Common Mistakes in Client Communication: How to Not Frustrate Your Client
• How to Hire a Great DevOps Engineer

Posted at 10:41PM May 15, 2019 by Zeger Hendrikse in Continuous Delivery  |  Comments[0]

Interesting posts on TopTal blog

• Ensuring Clean Code: A Look at Python, Parameterized
• A Better Approach to Google Cloud Continuous Deployment
• Zero Downtime Jenkins Continuous Deployment with Terraform on AWS

Posted at 08:25PM Mar 21, 2019 by Zeger Hendrikse in General  |  Comments[0]

OKRs versus KPIs

In this post a nice analogon can be found illustrating the difference between OKRs and KPIs:

Posted at 10:46AM Jan 30, 2019 by Zeger Hendrikse in General  |  Comments[0]

Interview questions

Interview questions:

• DevOps interview-questions
• AWS interview-questions
• Full-stack developer interview questions
• Core Java Interview Questions
• 12 Essential Docker Interview Questions
• 14 Essential GitHub Interview Questions
• 10 Essential MongoDB Interview Questions
• 21 Essential React.js Interview Questions

Posted at 07:14PM Jan 17, 2019 by Zeger Hendrikse in Continuous Delivery  |  Comments[0]

Brilliant comic introducing Kubernetes

Please find here a brilliant comic introducing Kubernetes.

Posted at 10:34PM Jan 04, 2019 by Zeger Hendrikse in General  |  Comments[0]

Deploying a COTS Application in the AWS cloud with Continous Delivery, IaC, Packer, GitLab, Ansible and Terraform

In this post we discuss how to deploy a COTS application in the Amazon cloud using a continuous delivery pipeline in GitLab, using Packer and Ansible to create an AMI (abstract machine image) and Terraform to lay out the infrastructure to which the application will be deployed.

Posted at 11:19PM Apr 30, 2018 by Zeger Hendrikse in Continuous Delivery  |  Comments[0]