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.
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
Welcome back to the Meet Our Team Q&A series. My name is Daniela Williams, Project Manager at ISE, and I’ll be asking ISE team members questions to help give insight into what makes us tick.
Today I'm interviewing Griffen Clark, Software Engineer, and one of our interns turned full-time engineers.
Developers often work individually or in a larger team to produce products for a variety of consumers. Sometimes it’s a web app, a mobile app, or perhaps software for an overall system that includes some hardware. When developers are creating something that will be out on the marketplace they know it will reflect on them or their company, and have an impact on whether or not trust is built in the marketplace. In this scenario, documentation in the form of help menus or instruction manuals may be extensive to make sure the user experience is ideal and that any issues or concerns raised are promptly addressed. In contrast to this, when it comes to working with other developers through documentation or direct support, completeness and attention to detail can often be lacking.
In my previous blog post I discussed several key takeaways from the 23rd ACM SIGKDD Conference on Knowledge Discovery and Data Mining (KDD 2017), including time series analysis, survival analysis, and massive online analytics. In this post, I will take a deeper dive into survival analysis. I’ll go into detail on what survival analysis is, how it originated, the components involved, different methods that can be utilized, real-world examples, and open source libraries available.