It's National Engineers Week! This morning our Fun Committee kicked off a week of celebrating the many engineers at ISE with bagels for everyone. I know they have a few more exciting activities planned for this week as well.
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
If you were to ask most people to name some popular social media platforms, you would likely get a quick response of Facebook, YouTube, Twitter, or MySpace (just kidding on that last one). Ask that same person to name some popular IoT platforms and prepare for a deer in headlights look. Even if a person has knowledge about the IoT space, they likely do not know what the market is offering in terms of platforms. That’s in large part because the market is still very much in the early stages.
When I first learned* about Scrum, the trainer provided us with some "rules of thumb" for planning our time during a sprint. As we started putting Scrum into practice, we applied these rules of thumb… but also encountered shock and horror from outside the team about how much "overhead" was involved. The arrival of Ken Rubin's recent blog post, How Much Time Should Each Scrum Practice Take? reminded me of these early experiences. In this blog post, I reflect on the perception vs. reality of this "overhead".
One of the biggest crowd reactions during November’s AWS re:INVENT conference was AWS CEO Andy Jassy’s announcement of Elastic Container Service for Kubernetes (EKS). For those not already familiar with it, this seems like a good opportunity to talk about what Kubernetes is, some of its use cases, and where it fits in the cloud and DevOps landscape.