InfoQ Homepage Conferences Content on InfoQ
-
Neal Gafter Discusses Closures, Language Features and Optional Typing
In this interview from QCon London 2008, Neal Gafter discusses upcoming language features in Java 7, superpackages, what closures are, the differences between the three major closures proposals (CICE, FCM and BGGA), optional typing systems for dynamic languages, and the next major language.
-
Guy Steele on Programming Languages
Sun Fellow Guy Steele is interviewed by Floyd Marinescu, co-founder of InfoQ, and Bobby Norton of ThoughtWorks. Guy works for the Programming Language Research Group. The interview focuses on programming languages, the lessons to be learned from the past and what to expect from the future.
-
Avi Bryant on DabbleDB, Smalltalk and Persistence
In this interview, Avi Bryant talks about the Smalltalk web framework Seaside, DabbleDB, using Smalltalk images for persistence instead of an RDBMs, GemStone and more.
-
Christophe Coenraets Discusses Flex 3, AIR, and BlazeDS
In this interview from QCon London 2008, Christophe Coenraets discusses Flex 3, Flex Builder, AIR, BlazeDS, the move towards open source at Adobe, how to integrate Flex with existing applications, and the challenges of integrating Rich Internet Applications with search engines and built-in browser functionality.
-
Mark Little on Transactions, Web Services and REST
In this interview, recorded at QCon London 2008, Red Hat Director of Standards and Technical Development Manager for the SOA platform Mark Little talks about extended transaction models, the history of transaction standardization, their role for web services and loosely coupled systems, and the possibility of an end to the Web services vs. REST debate.
-
Avi Bryant on MagLev and GemStone
In this interview, Avi Bryant talks about working on GemStone's MagLev, a Ruby implementation built on the GemStone S64 VM. Avi explains the reasons for MagLev, the merits of GemStone's persistence and distribution features, and the future with multiple Ruby implementations.
-
Randy Shoup Discusses the eBay Architecture
In this interview from QCon San Francisco 2007, Randy Shoup discusses the architecture of eBay. Topics discussed include eBay's architectural principles, horizontal and vertical partitioning, ACID vs. BASE, handling data inconsistency, distributed caching, updating eBay on the fly, architectural and coding standards, eBay's search infrastructure, grid computing, and SOA.
-
Rachel Davies on Generic Agile
In this interview taken by Deborah Hartmann during Agile 2007, Rachel Davies, director of Agile Alliance, talks about Generic Agile, about the necessity to understand what is important in a development process, rather than sticking with a strict Agile method.
-
Orbitz.com Architecture with Brian Zimmer
In this interview taken during QCon 2007, Brian Zimmer talks about the architectural challenges he has faced working on Orbitz.com, one of America's most popular online travel booking sites. He touches the subject of dynamic languages and their importance in augmenting Java in order to become a better and richer platform.
-
James Shore on “The Art of Agile Development”
In this interview taken during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book "The Art of Agile Development" he and Shane Warden wrote. The book was not yet published at the time when the interview was made, and James offers a valuable introduction to the book touching various aspects of Agile development.
-
Segundo Velasquez and Agile as Seen Through the Customer's Eyes
Segundo Velasquez came to the Agile 2007 conference to meet with an Agile team which promised him help to design and develop a web application meant to build a stronger relationship between Mano a Mano, a charitable organization, and its donors. Segundo shares his amazement on how quickly the whole process evolved.
-
Markus Voelter about Software Architecture Documentation
During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.
