One of the worst, most annoying, and inept security practices to evolve in online applications over the years is the process of security questions and answers for logging in and/or password & account recovery. They’re annoying, vague and restricted and they absolute must die, die, die!
There’s a lot you can do with Microsoft Flow and implementing the approval action. This will allow you to put in a process to control any Flow you want to. Most of the sample approval templates in Flow are focused around business processes.
A growing number of people seem to be using Instagram as their primary social media platform. It works well and is quite simple, without a lot of the extra baggage that Facebook and other platforms add. So long as your primary content is image based, it’s great at what it does. In this post, I’m going to be covering a couple of excellent ways to get started with integrating Microsoft Flow with Instagram.
Last time I walked through a more complex way to implement a roll your own ‘In Case You Missed It’ Flow for retweeting Twitter posts linking to new blog articles. It wasn’t the way I would do it, but the point was more to show you a few things you can do in Microsoft Flow. This time I’m going to show you an easier way to retweet posts to Twitter about your blog. And this time we’re going to use Azure Table Storage to make our lives easier.
One of the promotion methods that many bloggers employ with Twitter is to re-tweet their previous blog post tweets with an ‘In Case You Missed It’ (#ICYMI) tag a few hours or days later. In this blog post, and the next one, I’m going to show you a couple of ways you can implement this in Microsoft Flow.
In my last post, I showed you how to create a Flow that would promote a new blog post on Twitter and LinkedIn. Given the character limits on Twitter, you may run into issues where your tweet has too many characters and your Flow will fail. The quickest way to address that is to convert the link to the blog post into a short URL using the Bit.ly connector.
I recently found myself in the uncomfortable position of having to look for a new job. Thanks to the ‘alleged’ poor life decisions of a certain former leadership person, the company I had poured most of the last four years into was closing its doors. We’d limped along best we could for a time after the ‘event’, but it was not to be. It was time to put it out of its misery. Those of us that had survived that long suddenly found ourselves with a need to go job hunting.
For all of us, there will times, many times, when our efforts end in failure. Sometimes, they will be small failures. And sometimes, they will be spectacular failures. Sometimes, you will be at fault. And sometimes, despite all your best efforts, someone else will be at fault. It doesn’t matter. It’s just another opportunity.
It’s a great time to be in the tech industry in general. Unemployment is down in most areas in the tech sector. You have the advantage. Use it. As with all things, times change. There were times it wasn’t good to be in tech. Those times will likely come again. But for now, you’ve got it good. If you’re not happy where you’re at right now, do something about it. Go and find a new job.
In a previous blog post, I talked about taking time to unplug in order to avoid burnout. That’s not what this is about. This is about getting in the zone. It’s about those times when you are so deep into the code that you just keep going and going. This is about those times when you get an idea and you dive headlong in and don’t come up for air for hours. Stop it. Stop it right now. Take a step back. Take a moment to breathe.