Tyler Jewell, CEO of Codenvy, unveils in this 2-parts article the architecture of Codenvy - a cloud IDE –, providing details on its platform and plug-in architecture, workspace and cluster management, multi-tenancy implementation, IDE collaboration, release model and SCRUM process used for development.
The typical software delivery project captures requirements numerous times, describes tests in multiple places, is indiscriminate of what is in a particular build, and often requires a large amount of analysis to know who is doing what and why. Dave West looks at the problems this causes and argues for holistic, integrated ALM approach.
Web Testing Environment (WTE) project makes application security tools available to developers and QA testers. InfoQ caught up with WTE project lead Matt Tesauro to learn more about the project. 1
In this virtual panel discussion, InfoQ spoke with Len Bass, Grady Booch, Paulo Merson and Eoin Woods about documenting software architectures especially in Agile software development environments. 14
Simon Guest of Microsoft introduces SketchFlow as a tool for developers to create high-fidelity prototypes for their WPF or Silverlight applications. 10
The use of Flex and BlazeDS by Java programmers developing rich internet applications (RIA) is advocated and thirteen reasons (e.g. "it's open source" and "it runs in any Java App Server") are given. 15
Danijel Arsenovski attempts to dispel some of the myths around refactoring and how it applies to .NET developers. 10
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. 3
When several teams work in the same codebase there's always risk of chaos. Henrik's "Scrum & XP from the Trenches" approach is a simple way to ensure clean, releasable code with every iteration. 20
Many organizations loves best practices and thinks it helps. In this article, Dan North shows how they can not only fail to help, but even have a severe negative impact on your top performers. 17
Architecture is often described non-tangible in documents or is entirely technology-driven. Markus Völter describes a third approach; to evolve a formal language of your architecture. 10