Posts in opinion
There always has been some anarchy about the architect’s role –and even more distraction when we combine it with software and/or system. I’m not going to solve that. Not today …
As I described in Introducing BDD & TDD, understanding the common goals of Behavior & Test Driven Development
and defining your specific needs is the first and most critical step to start using this essential discipline.
Whenever the goal is to use new tools, it is simple: purchase them, shop for some hands-on training, and you are done.
Our ambition is different: we want to become Agile and Lean.
Then, it depends on the starting point too. B&TDD in greenfield development is relatively simple: start writing your tests and code!
However, starting with B&TDD in (Modern) Embedded Software can be more challenging due to the existing and often
extensive codebase that was developed before the emergence of B&TDD.
Then, the question ‘How to start?’ is more like ’How to get out of the waterfall?’
Is Behavior & Test Driven Development an essential aspect of professional software engineering? Leaders such as
#UncleBob compare it to ‘double entry bookkeeping’: a crucial discipline. He claims that when our industry doesn’t
professionalize quickly, we have the risk that B&TDD will be enforced by law (too).
So, it can be wise to learn to practice it quickly.
It is not easy to start when writing (long-lasting) embedded systems. We have other demands, codebases with a
lot of history. Still, we can (& should).
And we have an advantage, our Typically engineers are clever: When they understand the objectives, they will find a solution; that is their job!
Updated on 2020/07/15
This old article was never really published. As it fits my new MESS blogs, I reworked and posted it again. This is part-I; I expect other parts coming weeks.
As your embedded software codebase grows, the risk of introducing errors and bugs increases exponentially. Doubling
the number of developers will roughly double the risk of mistakes. We need new “tricks” to strive for the
ever-demanded high quality.
This is a constant battle. As embracing tools, processes, or disciplines helps only once.
Whether it’s your office printer, your internet router at home, or your future top-notch embedded system, they all
use technologies that, only a decade ago, nobody imagined using in an embedded system! How did this happen?
Regelmatig krijg ik ‘Embedded Linux Experts’ aangeboden; bijvoorbeeld voor het HTLD-team (HighTech Linux Delivery). Vaak zijn goede mensen, met Linux ervaring; maar toch niet de mensen die ik zoek. Het blijkt erg lastig voor niet direct betrokken, om de juiste experts te spotten. Daarom een paar hints waarmee je “de” Embedded Linux Expert herkent. Immers, alleen het woordje ‘Linux’ op een CV is onvoldoende!