Unexpected Lessons
Sometimes things don't go as expected. That can be frustrating and unfortunate...but also an opportunity to learn.
Sometimes things don't go as expected. That can be frustrating and unfortunate...but also an opportunity to learn.
How much can one jurisdiction affect the internet? Turns out, a lot. Recent actions by the US and Australia are having and could have a disproportionate impact on our online communities.
Security metrics are hard. But that doesn't mean you should ignore them. In fact, a lot of teams are measuring the WRONG things which leads them down a path where efforts are being spent in areas that aren't driving to their bigger goals.
Fortnite is an international sensation. Despite being truly free-to-play, they are making a lot of money by continually improving the game experience, balancing the in-game economics, and other critical factors.
Data privacy is a critical area of concern around the world. Look no further than four distinct events today: Australia passing a new law, an arrest for Huawei, Apple publishes a new paper, and the Government of Canada sets a new directive.
After a jam packed AWS re:Invent 2018, I've been thinking about how to deliver information to an audience. One of the challenges is delivering that information with enough context that it makes sense to that audience.
When you are trying to get a message out to a lot of people, it's not realistic to try and get them all back to you digital properties. So what do you do? How do you manage trying to hold the same conversations in multiple places? How do you monitor what's working?
The "secret" to most success is being prepared. Taking a few minutes or hours to map out what you want to happen is far better than trying to figure it out when you're up against the clock.
Before any big shifts there are always small signals that hint at what's coming. We're seeing more and more companies start to make a play for data. Whether it's as a broker, niche analysis, or in data aggregation. There is risk here if this rapidly growing area is left unchecked.
We build services and solutions using parts provided by other companies. That's the only way to move forward effectively. When a security or privacy breach happens, how do you handle those parts out of your direct control? Especially considering your customer may not have any idea they exist?
You know you have to master your tools but are you selecting or building the right tools? A lot of teams over or under engineer their tools. This results in either a failure to return the value invested or lost productivity. Are you hitting the sweet spot?
You can't really remove something from the internet. Not is the owner/operator really wants it out there. That's a huge advantage and challenge for the internet community. What are the impacts of that fact?