#55 2 rules to play by in SPFx

    2 SharePoint Framework rules of thumb that you must keep in mind to play nicely and don't break the page.

    #51 Why you should learn git

    A lot of technical content is shared on GitHub these days. And if you want to use it or contribute to it, you will need to learn git.

    #47 Ask for help

    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?”

    #44 Is your code ready for the worst?

    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.

    #43 You're in marketing

    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?

    #42 The answer is 'Yes'

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

    #40 Why should they care?

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

    #37 I just need this one more thing

    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.

    #36 Where do you belong

    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.

    #35 Don't tick the box

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

    #34 You shipped it, so what?

    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?

    #33 That's Great Feedback

    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?

    #32 Let's Not Overcomplicate Things

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

    #31 Seek to understand

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

    #29 Tools don’t unlock potential

    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

    #27 4 Reasons Why You Should Use An SDK

    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.

    #24 Learn building Microsoft Teams apps

    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?

    #23 All You Need Is A Plan

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

    #22 Tests Are A Waste Of Time

    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.

    #20 Never stop asking 'why'

    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?

    #19 Inbox zero is a trap

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

    #18 What are you learning now?

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

    #17 Getting started

    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.

    #16 People don't care about your stuff

    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.

    #15 I'll fix it later

    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

    #14 Get out of your bubble

    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?

    #13 Automated builds are a must

    No matter when you worked with the particular project the last time, deploy with confidence, every single time. Avoid stress and save time.

    #11 The price of a feature

    When building a physical product, you're limited by its design, material, weight. Unfortunately, this isn't the case when building software.

    #6 Build for Microsoft Teams

    Did you know that you can use SharePoint Framework to also build applications for Microsoft Teams?

    #5 Good idea just not now

    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?

    #4 Build it and they will come

    If you think that if you just build it people will come, I’m sorry to break it for you: you’re wrong.

    #2 What is it for

    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?