Whatever you’re building is hard to use. It’s not for you of course, because you’ve been working with it since forever, but it is for everyone else. Want proof?
No matter when you worked with the particular project the last time, deploy with confidence, every single time. Avoid stress and save time.
If you don’t want to use PnPjs for the fluent syntax then do it for your team or for your own sanity. I promise you won’t be disappointed.
When building a physical product, you're limited by its design, material, weight. Unfortunately, this isn't the case when building software.
Certain SharePoint features are available only if you're on modern. Are you on modern yet?
For a long time, you could work together only with your colleagues. But this is no longer the case. Here is why.
In the past, you might have built SharePoint-only applications, but that's no longer the case.
What's the first impression of the thing you're building?
Did you know that you can use SharePoint Framework to also build applications for Microsoft Teams?
Often we look at ideas as absolutes. Something we either do or don’t do, right now. We rarely dare to say something is good but not now. Why?
If you think that if you just build it people will come, I’m sorry to break it for you: you’re wrong.
Microsoft 365 Patterns and Practices: is it just a collection of resources or is it more?
Don’t tell me what something is. I see it’s a table or a chart. Instead, tell me what it’s for. What problem is it solving? What good is it for me? What’s the benefit? Why should I care?
It's only a matter of time before you hit a block using open source. But how do you get the maintainers to help you?