Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Documentation Content on InfoQ

  • Lean Documentation

    Knowledge about system and domain, which is important for both effectiveness and good quality, is best acquired through a dialog, face2face. Unfortunately, there are situations when a dialog is not possible and our only rescue is lean documentation. This article gives you 6 practices how to maximize information while minimizing the number of words. This makes it easy to use and to maintain.

  • Conversation Patterns for Software Professionals. Part 3

    The third article of the Conversation Patterns for Software Professionals series is focused on very powerful tool which is a Conversation Structure. Michael explains the structure and the mechanics of what people call “a talk”, shows how to control the conversation flow and how to navigate through a conversation on purpose.

  • Conversation Patterns for Software Professionals. Part 2

    All too often we that the business people we deal with do not know what they want, in this second article in a series Michael presents some ideas on how to talk to them and how to explore their needs. In this article he discusses formulating questions to be able to uncover the real needs and underlying motivations

  • Conversation Patterns for Software Professionals. Part 1

    All too often we that the business people we deal with do not know what they want, in this first article in a series Michael presents some ideas on how to talk to them and how to explore their needs. In this article he discusses how to manage a conversation, explore the needs and clarify expectations.

  • Book Review: Pro Website Development and Operations

    Overall the book is a quick read that provides some useful insights and potential starting points for enterprise practitioners and technical managers in medium to large enterprises where development and operations are still very defensive towards each other (often driven by conflicting goals) and where a blame culture reigns.

  • A Roadmap to Agile Documentation

    The agile mindset lies on the premise that all the tasks in an application lifecycle create some kind of value to the client. But when it comes to documentation, teams can find it hard to find such value. This article provides an agile approach to the production of different types of documentation, in different phases of an application lifecycle, adapted to the different target audiences.

  • I’d Rather Be Coding – Writing Things Down

    For lots of reasons, most developers hate writing down anything that isn’t code. The Agile Manifesto deemphasizes documentation, but there are times on a project when a little documentation can go a long way. In this article, we will explore why collaboration over comprehensive documentation shouldn’t mean “NO” documentation – and when you should stop coding and start writing things down.

  • Feature Injection: three steps to success

    Often Customers provide half baked solutions with no linkage to value. An Agile team needs examples linked to the Business Value they provide. Feature Injection is a process that takes a half baked solution identifies the Business Value it provides and then produces a set of examples driven from that value.

  • Implementation Decision Rationales – Program Comprehension in Agile

    Given the fact that the bulk of a developer's work is maintaining and enhancing existing code, Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to help later developers tie the source code syntax to its meaning in the application domain. Using simple tags and clearly thought out rationale to provide just-enough value.

  • Describing RESTful Applications

    If servers control their own namespace without a fixed resource hierarchy, how do clients, and more importantly client developers, get to learn or discover URIs of resources? In a new article, Subbu Allamaraju discusses how to describe a RESTful API, focusing on using hypermedia instead of an out-of-band description format such as WADL or WSDL 2.0.

  • 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.

  • EJB 3 Glossary

    An essential glossary of new terms and concepts introduced in EJB 3. The glossary demystifies buzzwords like (IoC), Configuration by Exception, POJO, POJI, Dependency Injection, Embeddable Object, Interceptors, and more. This glossary will constantly be updated.