Putting ourselves in the shoes of the user is key to building better systems and services.
In this podcast episode, Tim O’Reilly talks about building systems and services for people, keeping a close eye on the end user’s experience to build better, more efficient systems that actually work for the people using them. Highlighting a quote from Jeff Sussna, O’Reilly makes a deeper connection between development and the ultimate purpose for building systems and services — user experience:
“[Jeff Sussna says in his blog post Empathy: The Essence of DevOps]: ‘It’s not about making developers and sysadmins report to the same VP. It’s not about automating all your configuration procedures. It’s not about tipping up a Jenkins server, or running your applications in the cloud, or releasing your code on Github. It’s not even about letting your developers deploy their code to a PaaS. The true essence of DevOps is empathy.’
“Understanding the other people that you work with and how you’re going to work together more effectively. That word ‘empathy’ struck me and it made me connect the world of DevOps with the world of user experience design.”
How NoSQL databases scale vertically and horizontally, and what you should consider when building a DB cluster.
Editor’s note: this post is a follow-up to a recent webcast, “Getting the Most Out of Your NoSQL DB,” by the post author, Alex Bordei.
As product manager for Bigstep’s Full Metal Cloud, I work with a lot of amazing technologies. Most of my work actually involves pushing applications to their limits. My mission is simple: make sure we get the highest performance possible out of each setup we test, then use that knowledge to constantly improve our services.
Here are some of the things I’ve learned along the way about how NoSQL databases scale vertically and horizontally, and what things you should consider when building a DB cluster. Some of these findings can be applied to RDBMS as well, so read on even if you’re still a devoted SQL fan. You might just get up to 60% more performance out of that database soon enough. Read more…
Mark Burgess chats about Promise Theory, and Geoffrey Moore discusses a modern approach to his Crossing the Chasm theory.
As systems become increasingly distributed and complex, it’s more important than ever to find ways to accurately describe and analyze those systems, and to formalize intent behind processes, workflows, and collaboration.
Camille Fournier on becoming a “multiplier” — and why multipliers are more effective than managers.
There are times when we all wish we could clone ourselves so we could get more done at work. In a Velocity New York 2014 keynote, Camille Fournier, CTO at Rent the Runway, presented an alternative, practical solution, that she argued is far more effective (not to mention feasible): become a “multiplier” rather than a manager.
Technical skills are important, she said, but they’re not ultimately the bottlenecks you experience later in your career — eventually, time and focus become the main hurdles. To overcome these hurdles, Fournier argued that you need to take a step beyond managing and focusing on creating additive value, and focus on multiplying your value by increasing the effectiveness of the people working around you.
Mikey Dickerson on why he moved from Google to the West Wing, and where we need to be allocating our engineering resources.
In a keynote address at Velocity New York 2014, Mikey Dickerson described his journey from working for Google to working in the West Wing of the White House, leading the US Digital Services group. He told the story of how a three-day review turned into a nine-week “herculean effort” by a team working 17 hours per day, 7 days per week to get HealthCare.gov up and running. The challenges, he stressed, boiled down to a few big, though basic, things — building a monitoring system, creating a war room to provide development direction and organization, and establishing a sense of urgency to get the problems fixed. “This very formidable obstacle, when you pushed on it even a little bit, fell apart; it was made out of sand,” he said. “Nothing we did was that hard; it was labor intensive, but it was not hard.”
Max Firtman on the future of mobile and the importance of embracing change.
Companies and developers have plenty of mobile development challenges — OS platforms, the growing number of devices and screen sizes, and the myriad requirements of browsers, to name a few. Soon — or already — the Internet of Things is going to muddy the waters further. In a recent interview, Max Firtman, founder of ITMaster, stressed the importance of the growing ubiquitousness of IoT and the necessity that companies embrace the future:
”Maybe in 10 years, we’re going to see devices everywhere sending input information to apps that might be in the server, in the cloud — and those apps will carry some kind of intelligence, and will bring us back information on other devices that could be a smart watch, smart glass, a phone; we don’t know, yet, exactly what will be here. But there are a lot of challenges there for content owners or companies because you need to understand that you’re going to be everywhere.