InfoQ Homepage Tools Content on InfoQ
-
Profiling java.util.concurrent locks
IBM’s Yao Qi, Raja Das, and Zhi Da Luo describe jucprofiler, an alphaWorks tool designed to profile multicore applications that make use of the java.util.concurrent classes introduced in Java 5.
-
Virtual Panel on Software Architecture Documentation
Software architecture documentation is an important part of the enterprise application development process. In this virtual panel discussion, InfoQ spoke with panelists Len Bass, Grady Booch, Paulo Merson and Eoin Woods about documenting the software architectures especially in Agile software development environments.
-
Using SketchFlow to Create Better Prototypes
All good developers use some kind of prototyping as a communication channel to customers. Simon Guest of Microsoft introduces a new technology from Microsoft, SketchFlow, and shows how it could be useful to developers as well as the primary audience of designers. The discussion covers coverage (WPF and Silverlight), functionality, workflow, prototyping, and documentation.
-
13 Reasons for Java Programmers to Learn Flex and BlazeDS
Thirteen reasons, some general ("it's open source" and "it has great community support") and some technical ("programming model similar to Java" and "runs in any Java app server"), for why Java Programmers should learn Flex and BlazeDS are presented. Technical reasons include examples as part of the discussion.
-
RGen: Ruby Modelling and Code Generation Framework
This article introduces RGen, a modelling framework inspired by openArchitectureWare. RGen uses internal DSLs for defining metamodels and offers a full modelling stack for Ruby.
-
Debunking Common Refactoring Misconceptions
In comparison to Java, an emphasis on continuous refactoring is still relatively new in .NET. Besides having few ardent proponents, many myths linger around what refactoring really is and how it applies to the development process in general. Danijel Arsenovski, author of Professional Refactoring in Visual Basic, attempts to dispel some of these myths.
-
Software Development Lessons Learned from Poker
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
-
Version Control for Multiple Agile Teams
When several agile development teams work on the same codebase, how do we minimize chaos, and ensure there's a clean, releasable version at the end of every iteration? Here Henrik Kniberg outlines the scheme used in "Scrum and XP from the Trenches". This paper is not so much for version control experts as for the rest of us, who just want to learn simple and useful ways to collaborate.
-
Better Best Practices
Organizations often introduce Best Practices as part of a change program or quality initiative. These can take a number of forms, from cheat sheets to full-blown consultant-led methodologies, complete with the requisite auditing and accreditation. In this article, Dan North shows how best practices can not only fail to help, but even have a severe negative impact on your top performers.
-
Architecture as Language: A story
Architecture is often described non-tangible in Word documents or entirely technology-driven. Both are bad, but what can be done? Markus Völter describes how to evolve a language around your architecture, a formal language that as a side effect ends up being a good base for generating important parts of the system.
-
NetBeans: Ruby Developer's New Best Friend (Part 3)
In the third and final article of the Netbeans Ruby series, Roman Strobl, covers quick fixes, RSpec support, and additional plugins of use to Ruby developers.
-
Kanban Applied to Software Development: from Agile to Lean
In this InfoQ article Kenji Hiranabe applies lessons learned while working with Japanese manufacturers. While many Agile teams are optimizing only a portion of the value stream, Hiranabe proposes a simple way to adapt lessons from Lean Manufacturing's "Kanban" visual tracking system to make process visible to more of the organization, for better communication and process improvement.