No Code, Low Code & Machine Code
Everything looks solvable if you ignore most of the complications. Many things look impossible when you’re stuck in the weeds.
The current fashion for low/no code testing heralds the cyclical return to looking for solutions that require softer skillsets. When is this appropriate and when is it a recipe for disaster? What level of abstraction is just right?
Seb has been a consultant, coach, designer, analyst and developer for over 40 years. He has been involved in the full development lifecycle with experience that ranges from architecture to support, from BASIC to Ruby. During his career, he has worked for companies large (e.g. IBM, Amazon) and small, and has extensive experience of failed projects. He’s now Continuous Improvement Lead with SmartBear, helping apply the lessons he has learned to internal development practices and product roadmaps.
He’s a regular speaker at conferences, a contributing author to 97 Things Every Programmer Should Know (O’Reilly) and the lead author of The Cucumber for Java Book (Pragmatic Programmers). He blogs at cucumber.io/blog and tweets as @sebrose.