This article summarizes the key takeaways and highlights from QCon New York 2015 as blogged and tweeted by QCon's attendees. Over the course of the next 4 months, InfoQ will be publishing most of the conference sessions online, including video interviews that were recorded by the InfoQ editorial team.
This article series offers readers tactical approaches to building software that your customers love. Break down existing silos and create an environment for cross-collaborative teams: placing technology, business and user experience design at the core.
Enterprises have continued to accelerate their adoption of cloud infrastructure. As this shift continues, it's important to understand what this means to applications that run in cloud environments.
The book "the nature of software development" intents to help people to organize their thoughts about value and find ways to deliver value in software development.
Erik Wilde talks to Mike Amundsen about Profiles, Description, Documentation, Discovery, his Sedola project and the future of Web-level metadata for APIs.
At the end of 2007, a political and humanitarian crisis erupted in Kenya due to suspicions that incumbent presidential candidate Mwai Kibaki had rigged the recent elections.
The book Fifty Quick Ideas to Improve Your Tests provides suggestions that cross functional teams that are doing iterative delivery can use to manage and improve their testing activities.
Vert.x is a reactive, microservices toolkit for the JVM, that provides an asynchronous, scalable, concurrent services development model. 1
In this article, author describes the role of data analytics in healthcare space with emerging wearable technologies like biophysical interfaces, physiological sensors and embedded diagnostic tools.
In the fast growing world of APIs and microservices, finding just the right API when you are developing a web, or mobile application, is always a tedious task.
James Grenning talks about why people are not doing technical practices sufficiently or well enough, TDD and unit tests, and on becoming better in discovering "bad code”.