InfoQ Homepage Development Content on InfoQ
-
Software (r)Evolution: A Crystal Ball to Prioritize Technical Debt
Adam Tornhill introduces techniques based on software evolution and psychology that help to uncover problematic code, detect organizational issues and make practical decisions guided by data.
-
From Front-end to Full Stack with Elixir & Phoenix
Lauren Tan discusses how one can create web applications with Elixir and Phoenix.
-
Pony: How I learned to stop worrying and embrace an unproven technology
Sean T. Allen talks about his experiences using Pony to build Wallaroo, a high-performance, low-latency stream processing engine.
-
Refactor Front-end APIs & Accounting for Tech Debt
Julia Nguyen talks about accounting for technical debt in feature work and best practices in refactoring front-end APIs based on her work adding Apple Pay support to perk itemization at Indiegogo.
-
Exploring UI Composition in Aurelia
Rob Eisenberg looks at Aurelia’s approach to UI composition through an exploration of its component model with configuration models based on JavaScript decorators and metadata.
-
React+Redux at Scale
Daniel Cousineau looks at how React and Redux scale, not just in terms of quantitative performance, but in terms of architecture and team participation.
-
From Customer Self Service Portals to Web APIs
Florian Marquardt presents how Regiocom has created and uses web APIs to serve the energy market in several countries.
-
Becoming Fully Buzzword Compliant
Trisha Gee overviews the current technical landscape and presents a survival guide for those who want to stay ahead in this changing industry.
-
Reinventing Credit Insurance with APIs
Christophe Spoerry discusses embedding insurance in B2B innovations.
-
Elm and Phoenix: Two FP Flavors That Taste Great Together
Josh Adams discusses the basics of creating apps in Elm with a Phoenix back-end, using real-world examples of how the two work together in Firestorm, an open-source forum engine.
-
How to Survive the API Copyright Apocalypse
Steven Willmott recommends avoiding the possible API copyright troubles by sharing API definitions rather than copyrighting them.
-
Avoiding React Performance Pitfalls
Alex Grigoryan discusses the performance problems found and their solutions moving from Backbone/Java to React/Node.js at @WalmartLabs.