It’s a new year, a chance to have a clean slate. As humans, we want to make the most of this clean start to a fresh new year. What better way to start a new year out by analyzing what we did wrong last year and vowing to fix it in the coming year.
New Year’s Resolutions.
They can be personal or professional, secret or open for the world to know. They’re made with the best of intentions and the strongest of convictions.
And yet, only 8% of those that make resolutions will actually succeed.
Why do we tend to fail? What takes us from being hopeful and determined to slowly giving up? and how can we get those resolutions to stick?
In the 1970’s, a book called Psycho–Cyberkinetics by Maxwell Maltz sent a popular notion out into society: It takes three weeks to create a habit and three days to break one.
It’s a catchy saying and for some people, 21 days is ample time to create a habit. However, according to a 2009 study, the time it takes to form a habit really isn’t that clear-cut. Researchers from University College London examined the new habits of 96 people over the space of 12 weeks, and found that the average time it takes for a new habit to stick is actually 66 days; furthermore, individual times varied from 18 to a whopping 254 days.
Continue reading “Creating New Habits: Sticking to Resolutions in (and Outside) the Workplace”
Is there any more paradoxical time of year than Winter Solstice? At its heart, Winter Solstice brings the shortest day of the year mixed with the heightened anticipation of the holidays. It is a time of year where you have endless feel-good Hallmark movies and Christmas songs on every radio station, yet the cold, cloudy-quickly-turned-to-dark days makes average Midwest citizens prone to Seasonal Affective Disorder (SAD). Continue reading “Staying Focused & Overcoming the SADness of the Winter Season”
In my last post, I discussed how to setup JWT’s in ASP.NET Core 2. In this post, I’ll extend that example, adding the ability to refresh the JWT when it expires (i.e. refresh tokens). A refresh token will be returned with the JWT when the user logs in. And this new token will be used to refresh the JWT when it expires. We’ll simply create another middleware that handle’s the refresh token.
Continuing from my previous post, I’ll add refresh tokens to the application. The source code for this demo can be found here. Continue reading “Token Based Auth in ASP.NET Core 2 Part 2: Refresh Tokens”
In Part 1 we setup basic token authentication using JWT’s with asp.net. Things are setup reasonably but all is not well. As a developer, you could give the token a lifespan of 30 days and just force the user to re-login after those days but what if you make the user inactive and don’t want him to login anymore? There must be better way.
Generally, I token has a lifetime of about an hour and when it expires, we want to refresh that token, verifying that the user still has access to the system, etc. The method that this is handled is using refresh tokens. A refresh token is returned along with the normal token and it’s stored for when we must refresh normal token.
Starting from our previous app, let’s support refresh tokens. Note, the completed code for this blog can be found here.
This will require us to track refresh tokens in our database, so first, let’s create the RefreshToken model.
A couple weeks ago, Microsoft held their annual Ignite conference and I would usually be blogging about all the cool new things coming to Office 365. This year has been a bit a different experience altogether, not for a lack of features announced from Microsoft though…there were plenty of awesome new features announced. We’ve spent the past couple weeks fielding questions on Office 365 from existing customers and folks looking to make the move or at least understand the options available.
Continue reading “Office 365 Collaboration Confusion”
This afternoon I’m leading a Lunch & Learn at IBS friend and client Total Quality Logistics. I’ll be teaching them everything I know about Angular 2 and how we’ve utilized it in projects over the past few months. Should be a lot of fun! I’ll follow up later today with more details on how the event went.
If YOU are interested in having me or someone else from Nerdia (aka the IBS Mobile & Web Solutions Group) come for lunch to teach your team about Angular 2, Git, SharePoint and more, fill out the form here.
The front-end testing I’ve done in the past has always had some friction with respect to getting the tools setup properly. Mostly I have used Jasmine as the testing framework, which is pretty self contained – but to get a node test server setup properly there are a variety of other npm modules and karma configuration settings to deal with. I previously wrote about how the angular-cli makes it easy to get an Angular 2 project setup, and this includes getting the test tools setup as well. So instead of dealing with configuration settings, you can quickly get to just writing tests.
Continue reading “Angular 2 – Testing”