SpecFlow: Great concept, flawed execution.
SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts.
The problem: It falls short of its promise. ❌
The reality? Analysts rarely, if ever, write the specs themselves.
Instead, developers end up doing the job. So why not just stick to plain code?
What has been your experience with SpecFlow?
Power Platform Advisor
Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.
Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).
Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.
Services:
– Strategy and tactics advise
– Automating and integrating
A daily newsletter on automation and eliminating friction
Microsoft Teams: Too Many Apps in One? All-in-one apps like Teams? That’s a hard pass from me. Microsoft Teams wants to be the one app to rule them all. But I’m the guy who likes my apps separate, like LEGO bricks—not superglued together. I open my To-Do app...
I see your comment. And I see AI fingerprints all over it. You know the ones where you think: Bro... did you even read my post? 😅 I get it. We want engagement. We want the algorithm to give us more eyeballs. But fake engagement is still fake. Here’s what happens when...
Abstract the abstraction 🤯. .NET devs, we love our patterns... maybe too much. For a simple CRUD app, I've seen: Repositories – because obviously we can't query directly, that's too mainstream UnitOfWork – like transactions, but now with extra ceremony Services –...