InfoQ Homepage QCon Software Development Conference Content on InfoQ
-
A Crystal Ball to Prioritize Technical Debt
Adam Tornhill offers an overview of techniques that help uncover both problematic code and the social dimension of the teams that build software. He illustrates each point with a case study.
-
Refactoring Mount Doom - Tackling Legacy Code
Franziska Sauerwein discusses how to refactor code for the right reasons and the right methods to use for time efficiently.
-
Using Quality Views to Tackle Tech Debt @Tesla
Colin Breck discusses how quality views may help improve communication in support of tackling technical debt in an organization.
-
Strategic Code Deletion
Michael Feathers describes techniques that generate more certainty around assessments of feature liveness, and strategies that can be used to remove code that does not have high value
-
In-Memory Caching: Curb Tail Latency with Pelikan
Yao Yue introduces Pelikan - a framework to implement distributed caches such as Memcached and Redis. She discusses the system aspects that are important to the performance of such services.
-
Async or Bust!?
Todd Montgomery discusses several questions related to the asynchronous vs synchronous designs debate.
-
High Performance Managed Languages
Martin Thompson explores how their managed runtimes can equal, and even better in some cases, the performance of native languages.
-
Continuous Performance Testing
Mark Price talks about techniques for making performance testing a first-class citizen in a Continuous Delivery pipeline.
-
Performance Testing in Java
Ix-chel Ruiz and Andres Almiray talk about the tools, like JMeter and JMH, and some techniques that should make engaging in performance testing a rewarding experience.
-
Latency Sensitive Microservices
Peter Lawrey looks at the differences between microservices and monolith architectures and their relative benefits and disadvantages.
-
From Microliths to Microsystems
Jonas Boner explores microservices from first principles, distilling their essence and putting them in their true context: distributed systems based on reactive principles.
-
Building Reliability in an Unreliable World
Greg Murphy describes how GameSparks has designed their platform to be tolerant of many things: unreliable and slow internet connectivity, cloud resources that can fail without warning, and more.