InfoQ Homepage Conferences Content on InfoQ
-
Need Some Cache? Redis in Depth
Chris Meadows introduces Redis, explaining what it is good for, what does it take to be run, and what’s under the hood through a social networking code example.
-
Windows Azure
Scott Guthrie has a hands on session demonstrating some of the Windows Azure’s main features, such as storage, websites, services, SQL, blobs, cache, etc.
-
Accruing Technical Debt: Practical Decision-Making and Its Business Relevance
Christof Ebert discusses technical debt including a Netscape vs. IE case study and provides a framework with practices for managing technical debt.
-
Continuous Testing in Clojure
Bill Caputo discusses adopting continuous testing for Clojure, what are the goals of such a practice, how it differs from other languages, practical considerations (tools, setup) and a demonstration.
-
15 Lessons from 15 Years as a Software Architect
Ingo Rammer shares 15 tips regarding people, complexity and technology that he learned doing software architecture for 15 years.
-
Anarchy, Cooperation and the Bazaar
Ola Bini discusses using open source in distributed teams from a sociological, political, and organizational point of view, providing some lessons useful in daily development.
-
Connecting Millions of Mobile Devices to the Cloud
Damien Katz explains how Couchbase Syncpoint provides real time data synchronization capabilities between multiple mobile devices and the cloud.
-
The Generative Generation
Aaron Bedra shows code samples for writing Clojure tests using the test.generative framework, explaining why this framework and testing are useful.
-
A DSL for Scripting Refactoring in Erlang
Simon Thompson introduces Wrangler, a refactoring tool written in Erlang for Erlang code and embeddable in common IDEs, such as Emacs and Eclipse.
-
iOS Vulnerabilities and Fixes
Graham Lee discusses some of the vulnerabilities that may affect Objective-C programming, offering solutions to avoid them.
-
Beauty is in The Eye of the Beholder
Alex Papadimoulis attempts to define ugly code, how one can recognize it, providing advice on avoiding writing such code and refactoring old code to get rid of it.
-
Launching Kanban Teams
Jesper Boeg shares his experience, lessons learned, failures, and common problems met when introducing Kanban to various teams having no previous Agile or Lean experience