In-memory computing is evolving rapidly, providing the high-throughput and low-latency data processing needed to fuel IoT innovation. And, the open source Apache Ignite project is leading the way with a full-featured, in-memory data fabric that includes a data grid, compute grid, service grid, and messaging. But did you know it also provides streaming and complex event processing (CEP) features? With so many other streaming engines available (such as Spark Streaming, Apache Flink, or Apache Apex) why choose Apache Ignite?
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 Clay Schumacher, Senior Software Engineer, and head of Mobile Development at ISE.
Accountability and commitment. We hear these words a lot in the business and Agile world, but what do they mean, and how do we do them well?
We've all seen instances of "accountability" in the form of blaming and shaming: ("Whose fault is it?" and "What were you thinking?) These are the forms that accountability takes in a fear-based organization. The blaming and shaming approach to accountability creates unhealthy stress, shuts down creativity, and limits the success that people and organizations can achieve to only what is achievable via "safe" choices.
However, some people and organizations that have rejected a fear-based culture, and the blaming and shaming that go with it, may swing the other way, and avoid holding people accountable at all. I don't know how to hold you to account without blaming and shaming you, so I won't say anything at all, even though your work or follow-through has not met my expectations or the organization's standards. You might have experienced this dilemma. But surely this can't be the only alternative?
Well Formed Teams
How do you get a complex set of work done? Put a team on it. People working together to accomplish a common goal. We see it everyday, and everywhere. For most cases, that’s how work is done. Quoting Steve Jobs, “Great things in business are never done by one person. They're done by a team of people.” But is having a team enough for success? If any combination of people put together will produce a successful result, we would gravitate towards picking all the A listers and chaining them together. But that’s not generally the best combination. To understand the best makeup, we have to define what a Well Formed Team (WFT) means, which is a term used extensively in Agile/Scrum frameworks lately.