Articles by Alex Bunardzic
Avoid wasteful debugging activities by creating automated tests using TDD technique
Maximizing the utilization of the time spent on creating software is a surefire way to drive the team into a brickwall
We cannot know what customers actually value unless we expose them to our products and services. Here is how to do it in the most elegant way.
How to improve the flow of teamwork
A super-event to foster systems thinking and the removal of barriers and silos
Instructions on how to start, run and terminate Dojos
Quality of automated tests is the most important aspect of continuous delivery
Automating critical systems operations without having automated tests is risky practice
Adopt design principles to ensure highest quality of the code design
How to avoid the trap of getting stuck in an Expert Beginner role
Give equal care to the code structure as you would give to the code behaviour
Work challenges are opportunities to explore, experiment, and track the feedback gathered from the innovation
How to build a system that interacts with the outside world without knowing the gory details of the outside world
Switch focus from monitoring and measuring activities and outputs to measuring outcomes
Keeping the suite of automated tests lean is an essential trait of quality software engineering. Diligently remove all tests that don't add any value.
Knowledge must be shared rapidly to enable teams to continuously deliver desired values
First International TDD Conference generated a lot of good interest and traction
Design is not a static construct, it evolves by refactoring as we keep changing the code
What is the relationship between Observe-Orient-Decide-Act Loop and DevOps.
The importance of properly securing client-side applications has never been more urgent!
What does 'extreme' in Extreme Programming stand for? It stands for extreme interruptability and extreme steerability
Speed up the delivery process by avoiding queuing and needless looping
Any system operation we can perform manually can be fully automated by writing scripts
Why is changeable design desirable and what's preventing us from achieving it
Duplicated imperative conditional logic leads to proliferation of bugs
Extreme programming keeps going strong 25 years after its launch
Programming computers by feeding them plain text is very slow and needs to be sped up.
Visual example illustrating the fundamental differences between incremental and iterative development process.
Configuring complex workflows that govern Continuous Integration and Continuous Delivery must only be allowed by making changes to the YAML source files; GUI tools must be prohibited
WorkSafeBC DevOps 100th sprint celebration coincided with the 20th anniversary of the Agile Manifesto
Closer look into the principle of least knowledge
Teams share collective responsibility and therefore collectively own the code
Simple isn't easy, but it is the only way to build anti-fragile systems
Legacy code is hard to test, so extract methods by writing micro tests
The longer the wait to deploy, the bigger the risk of things going south
Developing a feature without formulating a hypothesis is like shooting in the dark
Change is stressful and risky, but avoing it is even riskier
Any discipline requires serious investment in time
Replace physical modularity with logical modularity