InfoQ Homepage Articles
-
The Java Evolution of Eclipse Collections
With each successive version of Java, frameworks must adapt and transform in order to stay current. This article aims to describe some of the new Java 8 features in Eclipse Collections, a high performance collections framework for Java, and looks ahead at some of the new things we’ve done to prepare for Java 9. This article will walk through these new features and changes.
-
Understanding Cloud Native Infrastructure: Interview with Justin Garrison and Kris Nova
"Cloud Native Infrastructure: Patterns for Scalable Infrastructure and Applications in a Dynamic Environment" from O’Reilly Media is a collection of guidance about building and managing modern infrastructure. InfoQ reached out to the authors to learn more about what they’re proposing, and how you can act upon it.
-
Offshoring Agile When You Are a Startup
Working with an offshore partner becomes faster and cheaper as communication technologies continue to improve. It is possible to achieve agility with an offshore team as long as you understand the limitations. Although some of the principles from the agile manifesto are difficult to reconcile with offshoring, they can still be used as guidance to work effectively together.
-
Detecting and Analyzing Redundant Code
As software development projects grow in scope, it is very easy for them to add redundant layers of code. By analyzing several large open source projects on GitHub, the author presents his findings as to the amount of redundant code each project has and shares some recommendations as to how all projects can improve their own code management.
-
Q&A on "The Complete Software Developer's Career Guide"
The Complete Software Developer's Career Guide answers questions that new and experienced developers often have in advancing their careers. Topics covered vary from learning technical skills, getting a job, and dealing with managers, to doing side projects or starting your own company.
-
A 4-Step Guide to Building Continuous Security into Container Deployment
Containers face security risks at every stage, from building to shipping to the run-time production phases. Securing them requires a layered strategy throughout the stack and the deployment process.
-
Scaling Agile – a Real Story
This is the first in a series of articles about making scaled Agile work with slicing, master planning, and big room planning. It is the true story from one particular program in a financial services company, the EU Mifid regulation of extended responsibility for investment advisors.
-
The Five Steps to Building a Successful Private Cloud
Increased competition among public cloud vendors, territorial regulations, and business demands have all contributed to a rise in multi-cloud strategies. In this article, Nicolas Brousse from Adobe explains five key components of successful private cloud implementation.
-
Q&A on the Book "Humans vs Computers"
Author Gojko Adzic has released a book, Humans vs Computers, in which he tells stories about the impact of inflexible automation, edge cases and software bugs on the lives of real people. He explains the common mistakes built into the systems and provides advice on how to prevent these mistakes from being built into our systems in the first place.
-
The Top 10 Adages in Continuous Deployment
On the basis of discussions at the Continuous Deployment Summit, researchers derived 10 adages about continuous-deployment practices. These adages represent a working set of approaches and beliefs that guide current practice and establish a tangible target for empirical validation.
-
Q&A on the Book SAFe Distilled
The book SAFe Distilled breaks down the complexity of the framework into easily understood explanations and actionable guidance. It’s a resource for acquiring a deep understanding of the Scaled Agile Framework, and how to implement it successfully.
-
Is TDD a Form of OCD?
Developers are increasingly testing their own and each other's code. "Evaluation anxiety" is common psychological condition that is directly impacted by self-testing and team-testing. Are practices like TDD a defense mechanism to protect coders from criticism? And do emerging methods like Behavior Driven Development represents a more emotionally healthy approach to team evaluation?