[フレーム]
BT

InfoQ Software Architects' Newsletter

A monthly overview of things you need to know as an architect or aspiring architect.

View an example

We protect your privacy.

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Unlock the full InfoQ experience

Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with content, and download exclusive resources.

Log In
or

Don't have an InfoQ account?

Register
  • Stay updated on topics and peers that matter to youReceive instant alerts on the latest insights and trends.
  • Quickly access free resources for continuous learningMinibooks, videos with transcripts, and training materials.
  • Save articles and read at anytimeBookmark articles to read whenever youre ready.

Topics

Choose your language

InfoQ Homepage Software Craftsmanship Content on InfoQ

  • State of the Practice - 2010

    A number of leading authors, practitioners, and speakers in the area of software development were asked a series of common questions about the state of software development practice in 2010. The interview took place at the Better Software / Agile West concurrent conferences in June 2010.

    on Jun 23, 2010
  • The Rugged Software Manifesto

    Security, is often either an oversight or an afterthought for most software projects. Most development teams would rather focus on getting more functionality on the table than spend time to evade a possible security breach. In order to help developers realize the importance of rugged software Joshua Corman, David Rice and Jeff Williams founded the Rugged Software Manifesto.

    on Jun 22, 2010
  • Naresh Jain Discusses "Simple Design & Testing" And The Conference Dedicated To It

    "Simplicity" is a core agile tenet, particularly when it comes to software design and testing. Since 2006, Naresh Jain has been running a worldwide conference, the Simple Design & Testing Conference, for practitioners to collectively push the boundaries on the topic. Naresh tells InfoQ what's going on behind this small, but well-known conference and why he is so passionate about the topic.

    on Jun 16, 2010
  • SEMAT - Software Engineering Method and Theory

    SEMAT was founded in November 2009 with the bold claim that the software industry has too many fads and immature practices. The signatories promised to refound software engineering and bring it into the modern age.

    on Apr 14, 2010
  • A Manifesto of Done

    Alixx Skevington posted a Manifesto of Done as the beginning of a discussion thread, talking about the commitments team members make to each other about the quality of their work and clearly expressing their commitment to delivering business value through their code. Covering areas such as coding standards, usable code, unit testing and test coverage he emphasises the importance of quality work.

    on Mar 19, 2010
  • Individual Rewards on a Scrum Team

    In a recent LinkedIn discussion the question was asked "Should we have an individual recognition reward on a Scrum team". This prompted some intense debate with points both for and against.

    on Nov 30, 2009
  • Software Katas - Practice in Public Makes Perfect

    Thought leaders in the agile community are talking about software katas - where one practices specific exercises until they are memorized. Robert Martin has calls them "performance art". Lately there has been an increase in blog posts and sites devoted to katas. The latest addition: weekly screencasts at katas.softwarecraftsmanship.org.

    on Nov 26, 2009
  • Empirical Studies on Software Quality Mythology

    Microsoft has released a summary of research findings that challenge traditional software-engineering mythology. Can code coverage really improve product quality? Does TDD take more time? What impact does a distributed team have on quality? Are assertions useful?

    on Oct 08, 2009
  • Opinion: Pair Programming Is Not For The Masses

    Pair Programming continues to be one of the most debated and controversial practices of recent years. Most proponents don't falter in their praise of the benefits, but many of even these same people will admit they struggle to get pairing really going in their shops. Why? Obie Fernandez opinions 10 reasons why this might be so.

    on Sep 23, 2009
  • PairWithUs: On-Demand Agile Software Development Video Examples

    One thing well known by most programmers is that the best (only?) way to learn programming technique is by example; specifically, watching someone else doing it. Antony Marcano & Andy Palmer's 'PairWithUs' gives people a great place to do just that.

    on Sep 16, 2009
  • 97 Things Every Programmer Should Know

    The 97 Things series continues, after the architect and the project manager, with things every programmer should know. InfoQ talked to its editor Kevlin Henney.

    on Sep 16, 2009
  • Software Craftsmanship North America

    Software Craftsmanship North America is a one-day conference with the goal of introducing the Agile community to the Software Craftsmanship movement. Interestingly, SCNA will be at the same time as the Agile conference, in the same city, and have many speakers that will also be speaking at the Agile conference.

    on Jun 22, 2009
  • Kent Beck Suggests Skipping Testing for Very Short Term Projects

    Kent Beck suggests that on very short term projects, when you're trying to figure out if there is a viable concept, you might do less (even no) automated testing to help get off the ground quickly. This goes against all of the conventional wisdom surrounding TDD.

    on Jun 18, 2009
  • FutureRuby Conference Coming Up

    After last year's success of the RubyFringe conference, organizers Unspace will hold the FutureRuby conference July 9-12 2009 - tickets are still available. We talked to Pete Forde of Unspace about what to expect from FutureRuby.

    on Jun 05, 2009
  • How TDD and Pairing Increase Production

    "Test-driven Development" and "Pair Programming" are two of the most widely known of agile practices, yet are still largely not being practiced by many agile teams. Often, people will cite being "too busy" to adopt such practices as TDD and pairing; in essence, implying that striving for high code quality will reduce productivity. Mike Hill explains how this logic is seriously flawed.

    on May 27, 2009
BT

AltStyle によって変換されたページ (->オリジナル) /