Strive for few dependencies
Every package that you add to your code is yet another dependency to your project.
This dependency is not for free.
You take on the risk of the dependency. Do you know the quality of the code? Do you know the experience of the programmer who made it? Will it be maintained?
Only take dependency on complex functionality, which would take a lot of resources to build yourself.
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
ReSharper is 20 years old! π Reading https://blog.jetbrains.com/dotnet/2024/07/23/resharper-20-years/ makes me realize how long I have been a .NET developer. I still remember using ReSharper for the first time. π‘ ReSharper made Visual Studio a much better IDE. π It...
Switching from Google to Bing π Recently, I've decided to switch from Google Search to Microsoft Bing, and hereβs why: Ad Overload on Google: Google's integration of its advertising and search teams has led to a surge in sponsored links. This trend often means...
Improving Optimization? The traditional steps of Optimization: 1. Eliminate 2. Automate or 3. Delegate What if we added a missing element? Simplify. Before automating a convoluted workflow or delegating a tangled task, strip away the unnecessary. Make processes leaner...