Developers are masochists π
They enjoy the thrill of the challenge… π’
Where the compiler turns them down 99% of the time π«, yet they persist to make it work. πͺ
Just a thought…π§
Developers are masochists π
They enjoy the thrill of the challenge… π’
Where the compiler turns them down 99% of the time π«, yet they persist to make it work. πͺ
Just a thought…π§
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 β...