InfoQ Homepage Culture & Methods Content on InfoQ
-
Does specific technology knowledge matter when recruiting?
Does technology matter when it comes to recruiting developers? Or is the way of thinking the only thing that’s really important? In a time when many job advertisements are flooded with technology buzzwords, Dan Creswell found an Amazons recruitment ad that solely focuses on thinking and understanding.
-
Presentation: Applying Agile to Ruby
In this presentation, Fred George talks about the application of agile practices in the enterprise and how they can help with the adoption of Ruby.
-
A case study of Apache peer/code review processes
Peter C. Rigby and Daniel M. German have released a case study of peer/code review processes used at Apache which looks at the types of reviews, frequency of them, and other characteristics. Although some question the data collection methodology, the papers offer an interesting set of discussions comparing and contrasting various review methodologies.
-
QCon San Francisco (Nov 7-9) Schedule & Speakers Posted
The schedule and 44 speakers (another 20 to be confirmed soon) has been posted for QCon, InfoQ's new enterprise software development conference coming to San Francisco Nov 7-9. Some of the speakers include Martin Fowler; Rod Johnson (Spring Creator); the architects of Second Life, Orbitz, Yahoo! & Linked-In; Erik Meijer (LINQ Creator); and many more!
-
Mingle 1.0 Released: Reactions
Mingle, agile project management software from ThoughtWorks Studios has been released. InfoQ covers the pricing, community reactions and features.
-
Iteration Types
What is an iteration in the Agile world? How is it different than previous ways the software community has performed iterations? Are there different types of iterations, and does it matter? The ScrumDevelopment list has been recently discussing type A, B, and C sprints (sprint = iteration in Scrum terminology) as defined by Jeff Sutherland and the ideas are relevant the the wider Agile community.
-
Book Excerpt: How to Improve your Continuous Testing
Continuous Integration has become a standard development best practice - but it's not always done well. Tests take up much of an application's build time, and poorly constructed test suites can cause long builds, whereupon teams start to circumvent agreed-upon CI practices just get the time to code. InfoQ presents advice and examples in Chapter 6: Continuous Testing from a new CI book.
-
InfoQ Interview: Experiences with Planning Poker
In this fourteen-minute interview, Nils Haugen described "Planning Poker," a simple mechanism for arriving at estimates collaboratively, which has additional team building benefits and improves team estimates over time. Haugen shared his views on why this technique is an important tool for Agile teams in this InfoQ interview.
-
Does software design really pay off?
Many developers have encountered a situation where they’ve been asked to cut down on design and "just get the job done". Martin Fowler presented his doubts about this strategy and explained trading design quality for speed is illusory for projects longer than just a few weeks.
-
Has Agile Crossed the Chasm?
Carrying on from last year's survey, Scott Ambler published the 2007 Agile Adoption survey this month. InfoQ provides some analysis of his findings and asks readers how they would approach getting a single view of Agile trends from across the community.
-
Article: Implementing Automated Governance for Coding Standards
Most development organizations of a significant size have some form of coding standards and best practices. Simply documenting these standards and keeping them up to date can be a significant challenge and enforcing them even harder. Our organization has found that enforcing coding standards and best practices in an automated fashion through our build process has been highly effective.
-
Testing and Quality Control the only Certification Needed?
A new certification for software developers that is neither about in depth knowledge of programming languages, nor any modelling and design techniques, was suggested by Reginald Braithwaite. Only one subject would be on the examination list - "Testing and quality control". Safety has to be the prerequisite to any software development job. For the rest marketplace will decide.
-
Kaizen in Lean Software Development
Lean methods employ Kaizen, or continuous improvement, to reduce waste and improve results on a regular, even daily, basis. On the leanagilescrum group, Alan asked, "Are there known techniques for facilitating kaizen activities within Lean/Agile software development?"
-
InfoQ Launches Architecture Community
InfoQ has launched a 6th community on 'Architecture', the intention of which is to serve as a source for tracking change and innovation of interest to those with an architecting/design role but not specific to any of our other communities on InfoQ which currently include Java, .NET, Ruby, SOA, and Agile.
-
Code reuse highly overrated?
Dennis Forbes bucks the conventional wisdom that has caused the industry to trend toward architectures focused on asset reuse, asserting that code reuse is highly overrated and rarely pans out as advertised.