Chat sites in south africa no signup no registration female doctors dating male nurses
What if developers, and others working on whole product teams, looked at their next iteration by asking "What is our next best investment? Is it learning from discovery, or learning "outside the code", or is it learning in production, or "inside the code".Let's explore how each person at this conference can use their skills, experience, empathy, and cleverness to make the next best investment in learning, and avoid getting more done that may not make real and lasting impact for the people using their product(s).After attending the talk, you’ll see that production issues are learning opportunities.You’ll be ready to spot them, understand them and use them to build better software. He has built applications in a variety of technology stacks for companies in the financial services, education, health and media sectors.David was awarded The Gordon Pask Award and has contributed to Agile at Scale, Story Mapping, and many other publications and presentations that can be found on-line.Like it or not, things will always go wrong in production.
He has spent the last 15 years coaching agility and producing products for companies of all sizes around the world. His focus on getting to know a project community allows him to seed self-discovery and avoid falling into the expert trap of simply telling people what they “should do".
Rouan is going to tell you about the types of issues that you should expect.
He’ll show you a range of techniques for finding out quickly that something has gone wrong, including everything from automated alerting to an old-fashioned phone call from a grumpy user.
Rouan will also cover diagnostic tools that can help you figure out what went wrong, talk about how your team could approach issues, and explain the possibility of creating self-healing mechanisms.
Lastly, he’ll chat about what you need to ship a fix fast and how the right production monitoring can even help you write less code.
If you wanted to keep costs down that server would have to be small, but that meant you couldn’t handle large traffic.