Newsletter

If you’ve been doing something for a long time, it’s scary to ask for help. “What would they think? Shouldn’t I know this? What about my image?”

Did you know that you can connect your app to Microsoft 365 with just 4 lines of code?

What would you do if you had a million?

Exceptions will happen, it’s just a matter of time. And when they do, you want to be prepared. Don’t just test the happy flow. Test for exceptions.

What have you done recently? What difference does it make? How does it help others? Why does it matter? Did you tell others about it? Did they get it?

When you're gathering requirements for a product, feature, or project, the last question you should be asking is 'Would you like...'?

Have you considered connecting your app to Microsoft 365? Here's the easiest way to learn how to get started.

“Build richer pages”, “Easily access the relevant information”, “Automate mundane tasks”, “Stay in the know”... why would I want it?

There are a few things you need to take care of when connecting your app to Microsoft 365. Luckily, there is a shortcut.

There’s just one thing that’s needed for adoption. It’s that simple and at the same time that hard.

I just need this one more thing before I launch/ship/send/share. Just need to add this feature, cut 0,5sec of performance, fix this one sentence.

Often, we're hesitant about getting labeled. After all, we're a whole person. But the way we identify ourselves says something about our belonging.

When you do things you don't believe in, when you tick the box, it shows.

Congratulations! You shipped it. The weeks, maybe months of your hard work are over. You released your project for everyone to see. You’re done, aren’t you?

When you ask others for feedback, do you shun what they’ll tell you? Or have you given up asking for feedback a while ago already?

Starting doing things immediately gives us the adrenaline rush, we’re busy, we’re moving towards our goals, right, a bias for action!

When someone brings up an argument or an idea different than yours: what do you do?

No matter what tools you get, they won’t help you unlock your potential. They won’t make you a better writer, they won’t make your app better

No matter what tools you get, they won’t help you unlock your potential. They won’t make you a better writer, they won’t make your app better

If you’re used to shipping or bill hours for work, taking time to think feels unproductive. It isn’t. Here’s why.

Today, over 115 million users work with Teams every day. And did you know, that you could help them work more effectively? Hear me out.

Today, over 115 million users work with Teams every day. And did you know, that you could help them work more effectively? Hear me out.

Here’s the easiest way to join a community

Even if your job seems mundane, there is a huge learning opportunity just around the corner. What can you do that seems impossible? How can you make it work? What new will you learn?

When your workday is over, do you leave your work at work or do you carry with you back home?

Every change you make to the system has a 50-50 chance of blowing up in your face. Maybe not immediately, maybe not tomorrow, but it will eventually.

Time, you can spend it only once and there are more choices available to us than ever before.

Why should this feature be added? Why should this data be presented? Why should it be done that way and not the other? How will it help users?

If your goal is to get to inbox zero or get everything off your to-do list, you’re in a trap.

Before you know, weeks or months have passed and you haven’t learned anything new. And it’s a shame.

Take some new piece of tech, a platform, product, framework, whatever. Try doing something with it. Unless it's trivial, which more than often is not the case, you will get stuck.

Well, maybe not as much as they don’t care as they don't live it. They have their own lives, jobs, and concerns, and typically, whatever it is that you want from them is not amongst their priorities.

You're in a rush, the code should’ve been shipped already or maybe it’s just a proof of concept that will be thrown out anyway. You'll fix it later

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?