In my post on passwords, I said: As it stands today, the real challenge is the initial identity verification. There is no single good way for, say, a banking application, to confirm the identity of the user opening the banking app for the first time on their smartphone […]
My employer told everyone to work remotely to protect the employees. I understand and appreciate the announcement. Having worked remotely for five years for my previous employer, I am a bit apprehensive about it. In this post, I hope to describe the challenges we had, what to anticipate, and how to cope.
“Covid19” is gripping America in a mass hysteria. Maybe some good will come out of the experience.
Passwords are the scourge of Internet security. They are easy to forget, they are too many of them, and they are relatively easy to steal or guess.
In the past three years, I have been doing more and more of my work in Golang. If I had to pick a language for backend microservice development (which is where 99% of my career has been), I would now gladly choose Go.
An elephant graveyard, when applied to a corporate setting, is a team, company, or some other set of conditions in which otherwise bright engineers are forced into positions or assignments where there is no hope for future career growth. In this post, I hope to define the conditions that must be present for an elephant graveyard to form, how to detect them, and how to navigate them.
Now that Peloton filed for IPO, there is a whole lot of opinions in the media from people who don’t own the product or subscribe to the digital service. I don’t intend to offer an investment opinion in this post. I do, however, want to dispel some of the FUD (Fear, Uncertainty, and Doubt) being spread around by so-called “experts” and “journalists.”