<?xml version="1.0" encoding="utf-8" ?>  
 <rss version="2.0"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
 <channel>
    <title>Web 2.0 announcer feed for methodology</title>
    <link>http://methodology.web2announcer.com/</link>
    <description>Web 2.0 announcer top stories for methodology</description>
    <dc:language>en</dc:language>
    <pubDate>Thu, 07 Aug 2008 22:39:16 GMT</pubDate><item>
	<title>Core Software Design Principles</title>
    <link>http://web2announcer.com/go/2733549</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    While a software system may have its own set of unique principles to guide its design, we believe that all systems can benefit from the use of this core set.
	</content:encoded>
    <pubDate>Thu, 07 Aug 2008 22:39:16 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2733549</guid><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://standards.web2announcer.com/">standards</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>10 ways to screw up despite Scrum and XP</title>
    <link>http://web2announcer.com/go/2733088</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Henrik Kniberg, author of Scrum and Xp from the Trenches, talked today at Agile 2008 about the most common ways for teams to fail despite applying agile practices and tools. His presentation was organised as a talk about common problems and symptoms of those problems, with audience voting on what hurts them the most. From my perspective, it was a very effective way to see problems of other teams and definitely raised the awareness of some of these issues.
	</content:encoded>
    <pubDate>Thu, 07 Aug 2008 12:42:47 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2733088</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Why Not Just Fire All Of Your Programmers?</title>
    <link>http://web2announcer.com/go/2732748</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Experienced programmers shouldn&#039;t just be responsible for writing code. It should also be the job of experienced programmers to take those who are less experienced or interested and pull them up to our level. Forcing them out of the profession is just as much of a failure on our part as it is on theirs.
	</content:encoded>
    <pubDate>Thu, 07 Aug 2008 03:20:53 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2732748</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://research.web2announcer.com/">research</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Rules for Spartan Programmers</title>
    <link>http://web2announcer.com/go/2732403</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    A month ago, Jeff Atwood (Coding Horror) wrote a blog post about Spartan Programming. The idea is to tend toward minimalism coding style: Minimalism isn&#039;t always the right choice, but it&#039;s rarely the wrong choice.&amp;#xD;
&amp;#xD;
 &amp;#xD;
&amp;#xD;
I figured out that many of Spartan Programming tenets can be expressed as CQL rules
	</content:encoded>
    <pubDate>Wed, 06 Aug 2008 18:42:46 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2732403</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Scrum in a Multiproject Environement</title>
    <link>http://web2announcer.com/go/2732347</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    A research paper on a very concrete and practical issue. Tells what exactly to beware of, when adopting Scrum in a multi-project environment and has a solid research background behind its claims.
	</content:encoded>
    <pubDate>Wed, 06 Aug 2008 17:27:20 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2732347</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://research.web2announcer.com/">research</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Introduction to IoC/DI - The art of Decoupling.</title>
    <link>http://web2announcer.com/go/2732322</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Introduction to IoC/DI - The art of Decoupling.  This episode we will review what Inversion of Control (IoC)/Dependancy Injection (DI) is and why they are important.
	</content:encoded>
    <pubDate>Wed, 06 Aug 2008 17:08:19 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2732322</guid><category domain="http://net.web2announcer.com/">.net</category><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://microsoft.web2announcer.com/">Microsoft</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>How to plan an agile project</title>
    <link>http://web2announcer.com/go/2732151</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    If you need to calculate the overall cost and timescales for an agile project, for example to get a project funded, how do you do it?
	</content:encoded>
    <pubDate>Wed, 06 Aug 2008 13:50:49 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2732151</guid><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Honest Estimations</title>
    <link>http://web2announcer.com/go/2732069</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Have you ever sat in a meeting, estimating the time that you will need to implement a feature? With only a vague idea of what it&#039;s all about and someone wants to know how long it&#039;s gonna take, so you have to come up with a number? And you are sitting there with a strong urge to start a discussion about each estimation, because you have the feeling, that you are the only one in the room who sees things straight?
	</content:encoded>
    <pubDate>Wed, 06 Aug 2008 11:33:45 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2732069</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>What Integrated Circuits Say About Testing Your Code</title>
    <link>http://web2announcer.com/go/2731641</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    A while back I talked about how testable code helps manage complexity. In that post, I mentioned one common rebuttal to certain design decisions made in code in order to make it more testable.&amp;#xD;
&amp;#xD;
    Why would I want to do XYZ just do improve testability?&amp;#xD;
Recently, I heard one variation of this comment in the comments to my post on unit test boundaries. Several people suggested that it’s fine to have unit tests access the database, after all, the code relies on data from the database, it should be tested.
	</content:encoded>
    <pubDate>Wed, 06 Aug 2008 00:42:57 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731641</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>On Our Project, We&#039;re Always 90% Done</title>
    <link>http://web2announcer.com/go/2731267</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Although I love reading programming books, I find software project management books to be some of the most mind-numbingly boring reading I&#039;ve ever attempted. I suppose this means I probably shouldn&#039;t be a project manager. The bad news for the Stack Overflow team is that I effectively am one.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 16:28:58 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731267</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://reviews.web2announcer.com/">reviews</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>DSL Book Roadmap</title>
    <link>http://web2announcer.com/go/2731236</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    I&#039;ve hit a significant, if purely internal, milestone in the DSL book recently. I also find that people regularly ask me what the status is of the book is. So it seems like a good moment to post a note about where I am with the book and where I see things going.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 16:19:32 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731236</guid><category domain="http://books.web2announcer.com/">books</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://other-languages.web2announcer.com/">other languages</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Five Things Linus Torvalds Has Learned About Managing Software Projects</title>
    <link>http://web2announcer.com/go/2731192</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Linus Torvalds explains how he keeps the people and software on-track, with the software quality Linux demands.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 14:56:02 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731192</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://open-source.web2announcer.com/">open source</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Anti-Java Professor: Still Off-Base</title>
    <link>http://web2announcer.com/go/2731145</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    The Anti-Java Professor is back. He says Java is the ruination of our programmers. Here&#039;s a rebuttal by an aerospace engineer.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 14:28:20 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731145</guid><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Onion Architecture : part 3</title>
    <link>http://web2announcer.com/go/2731147</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    In my previous installments, I described what has become my approach to defining the architecture for an application.  Based on feedback, I&#039;ve modified my diagrams a bit to reduce ambiguity and emphasize key points.  The goal of part 3 of this series is to compare and contrast the Onion Architecture with traditional layered architecture.  I will flatten the Onion Architecture to see what it looks like compared to traditional layered architecture, and I will force the layered architecture into an onion.  Whereas the shape can be either, the structure of the actual application is radically different from what is commonly known and accepted.  I&#039;ll define four tenets of Onion Architecture at the end.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 14:20:58 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731147</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Wearing Out My Delete Key</title>
    <link>http://web2announcer.com/go/2731150</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    I think every programmer should take every pairing opportunity they get. This article is about a realization I had while pair programming with Daniel Haran on the way to RubyFringe.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 14:07:44 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731150</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>FEST-Swing 1.0b1: GUI Testing Made Easy</title>
    <link>http://web2announcer.com/go/2731092</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    FEST-Swing is an Open Source Java library, released under the Apache 2.0 license, that provides a fluent interface for functional Swing GUI testing. This library provides an easy-to-use API that makes creation and maintenance of GUI tests easy.
	</content:encoded>
    <pubDate>Tue, 05 Aug 2008 13:06:16 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2731092</guid><category domain="http://announcement.web2announcer.com/">announcement</category><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Multiple Returns from a Single Method</title>
    <link>http://web2announcer.com/go/2730149</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Many people object to the suggestion that multiple return statements in a single method can help simplify code. Where did the idea come from? Is it still valid?
	</content:encoded>
    <pubDate>Mon, 04 Aug 2008 14:33:14 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2730149</guid><category domain="http://net.web2announcer.com/">.net</category><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://other-languages.web2announcer.com/">other languages</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Quantity Always Trumps Quality</title>
    <link>http://web2announcer.com/go/2729973</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Although I am not at all ready to call software development &quot;art&quot; -- perhaps &quot;craft&quot; would be more appropriate, or &quot;engineering&quot; if you&#039;re feeling generous -- the parallels between some of the advice offered here and my experience writing software are profound.
	</content:encoded>
    <pubDate>Mon, 04 Aug 2008 05:33:48 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2729973</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Evolution Of LINQ And Its Impact On The Design Of C#</title>
    <link>http://web2announcer.com/go/2729778</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    I was a huge fan of the Connections series, hosted by James Burke, when it aired on the Discovery Channel. Its basic premise: how seemingly unrelated discoveries influenced other discoveries, which ultimately led to some modern-day convenience. The moral, if you will, is that no advancement is made in isolation. Not surprisingly, the same is true for Language Integrated Query (LINQ).
	</content:encoded>
    <pubDate>Sun, 03 Aug 2008 22:03:53 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2729778</guid><category domain="http://net.web2announcer.com/">.net</category><category domain="http://database.web2announcer.com/">database</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://other-languages.web2announcer.com/">other languages</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Code Reviews are not just about the code</title>
    <link>http://web2announcer.com/go/2728947</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Usually when I am doing a code review, I ask not just access to the code, but to the source control repository as well. There are quite a lot that you can learn from the source control of a project. Here is something that is both good and bad. It is bad because we have no checkin comments. It is good because we can see that we have very frequent checkins.
	</content:encoded>
    <pubDate>Sat, 02 Aug 2008 17:54:50 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2728947</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Agile Success Factor: Continuous Integration</title>
    <link>http://web2announcer.com/go/2728748</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Agile has grown and evolved from a very simple developer centric process defined by Extreme Programming to a complex product brand that enterprises are using to bring more resiliency to governance programs, enterprise architecture initiatives, and application portfolio management efforts. But at its roots, there remains a key fundamental aspect that defines the essence of agility on the software development project. Continuous Integration is a strategy where software is integrated and built continuously, or at least as frequently as is feasibly possible.
	</content:encoded>
    <pubDate>Sat, 02 Aug 2008 12:17:40 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2728748</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://reviews.web2announcer.com/">reviews</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Looks Good To Me - Source Code Review Tools</title>
    <link>http://web2announcer.com/go/2728353</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Code reviews are the rule at Google -- peer review reduces bugs, increases code quality, reduces maintenance cost, opens up team communication, and helps get the job done right the first time.
	</content:encoded>
    <pubDate>Sat, 02 Aug 2008 00:40:57 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2728353</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Last.fm&#039;s Quality Control</title>
    <link>http://web2announcer.com/go/2728165</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    The use a very unique 3 bear display for quality of builds!
	</content:encoded>
    <pubDate>Fri, 01 Aug 2008 20:16:58 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2728165</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Best of Agile 2008</title>
    <link>http://web2announcer.com/go/2728055</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Agile 2008 is the premier conference of the Agile world with about 400 sessions to choose from. In this list of the top sessions I am highlighting the sessions where I will go and the sessions worth high attention. I tried reducing the list size really hard and it made me remove many really good sessions.
	</content:encoded>
    <pubDate>Fri, 01 Aug 2008 17:36:44 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2728055</guid><category domain="http://announcement.web2announcer.com/">announcement</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://reviews.web2announcer.com/">reviews</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The UML Diagram They Don’t Teach You in School</title>
    <link>http://web2announcer.com/go/2727976</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Class diagrams help you understand the code, but what if there are no significant classes, just a bunch of methods?  Enter the method-call diagram.
	</content:encoded>
    <pubDate>Fri, 01 Aug 2008 16:18:14 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727976</guid><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Caching Database Queries in Java</title>
    <link>http://web2announcer.com/go/2727837</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Caching database queries can reduce and even remove the performance degradation caused by slow database access. This article discusses steps needed to address the performance problem caused by the heavy database queries such as optimizing and caching database queries and provides code examples.
	</content:encoded>
    <pubDate>Fri, 01 Aug 2008 13:23:16 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727837</guid><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Thinking About Concurrency Oriented Programming</title>
    <link>http://web2announcer.com/go/2727677</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    A realization hit me this morning while I was brushing my teeth. I was meditating on the relationship between classes and objects in OO languages and Erlang’s modules and processes.
	</content:encoded>
    <pubDate>Fri, 01 Aug 2008 08:52:50 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727677</guid><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://other-languages.web2announcer.com/">other languages</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>How I wrote 2 web apps at the same time</title>
    <link>http://web2announcer.com/go/2727443</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Since announcing the launch of Cart45 last week, I’ve had quite a few people asking how I’ve managed to create an ecommerce app and another web app (Bean Counter) seemingly simultaneously. &amp;#xD;
&amp;#xD;
A lot is down to my downright bizarre working arrangement whereby my employer allows me to spend 20% of my time pursuing my own projects.
	</content:encoded>
    <pubDate>Fri, 01 Aug 2008 01:46:38 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727443</guid><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Why is Static Analysis Uncommon?</title>
    <link>http://web2announcer.com/go/2727102</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    This is another of those very interesting poll results coming up on java.net regularly.
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 17:39:47 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727102</guid><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Demystifying JFormattedTextField: A Step by Step tutorial</title>
    <link>http://web2announcer.com/go/2727030</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    JFormattedTextField is a very useful Swing component, that let’s your users see data in a format suitable for them, while letting you read or write from it in a way that that suitable for your code. Let’s make sure that you clearly understand everything related to it.
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 16:15:51 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727030</guid><category domain="http://gui.web2announcer.com/">gui</category><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://usability.web2announcer.com/">usability</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Software Development Cycles</title>
    <link>http://web2announcer.com/go/2727034</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    The inside details of the software development cycle
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 15:31:44 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2727034</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Onion Architecture : Part 2</title>
    <link>http://web2announcer.com/go/2726978</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    In part 1, I introduced an architectural pattern that I have named &quot;Onion Architecture&quot;.  The object-oriented design concepts are not new, but I&#039;m pulling together a lot of techniques and conventions into a single pattern and giving it a name.  My hope is that the industry can use this name to communicate the architectural approach where appropriate.
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 15:03:07 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726978</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Why you shouldn’t code in Spanish</title>
    <link>http://web2announcer.com/go/2726926</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    A brief article about why you must write your variables, comments, etc.. in English in your code. Beleive me, there are heaps of applications written in other languages than English!
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 14:05:00 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726926</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://open-source.web2announcer.com/">open source</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Is The Need For Projects Dead?</title>
    <link>http://web2announcer.com/go/2726821</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    In an agile development environment, are Projects still needed?
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 12:02:23 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726821</guid><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>7 Ways to Improve Your Software Release Management</title>
    <link>http://web2announcer.com/go/2726744</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Two consultants helped turn around the release management of a major U.K. telecommunications provider, where completed software had languished for as much as three months before it reached its users. They share their experience in turning around deployment processes and their top tips for improving your software releases.
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 10:24:51 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726744</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Agile and CMMI: Better Together</title>
    <link>http://web2announcer.com/go/2726528</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Organizations follow many paths in their pursuit of excellence, applying various principles, methods, and techniques along the way. It stands to reason, then, that an organization interested in adopting agile practices might also be interested in PMI’s OPM3, ISO or Capability Maturity Model® Integration (CMMI) as a means to achieve that excellence. While I have seen some organizations that are trying to implement agile and a PMI model at the same time, none are doing it successfully. Last year, in fact, I observed two very large companies that had simultaneous internal initiatives to utilize agile and CMMI. At both companies, each group saw the other as competition. I left both organizations frustrated. I
	</content:encoded>
    <pubDate>Thu, 31 Jul 2008 04:33:16 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726528</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://reviews.web2announcer.com/">reviews</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Scrum in 5 minutes(pdf).</title>
    <link>http://web2announcer.com/go/2726188</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Scrum in 5 minutes....
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 20:28:05 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726188</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Lessons Learned from Architecture Reviews</title>
    <link>http://web2announcer.com/go/2726102</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    n this presentation, Rebecca Wirfs-Brock presents some practical lessons she has learned from doing architectural reviews. Many times projects are not delivered in time, or have quality problems or have an incomplete set of features due to architectural flaws. The reviews are meant to highlight existing risks and strengths of the architecture, and to reveal issues initially neglected.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 18:05:39 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726102</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Testing Anti-Patterns: The Ugly Mirror</title>
    <link>http://web2announcer.com/go/2726028</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Whether it’s strings, dates, timestamps, or numeric calculations, any time we can assert on a literal value, our test will be better off because of it. The less logic that’s in our assertion, the fewer chances we have for that logic to be wrong, and the less logic we have to dig through to grok what’s being tested in the first place.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 16:43:54 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2726028</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Economics of Testing Ugly Code</title>
    <link>http://web2announcer.com/go/2725981</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    The testing of code, whether formal or informal, tends to create a &quot;value spike&quot;. This is a problem if the code is &quot;ugly&quot;, and we want to change the code-base to make it less ugly. I discuss some possible solutions to this problem, illustrating the issues with graphs of a hypothetical code-base, showing value as a function of ugliness.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 15:33:29 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725981</guid><category domain="http://agile.web2announcer.com/">agile</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Software Development Standards</title>
    <link>http://web2announcer.com/go/2725877</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    It&#039;s said like this: “Industry Standards &amp;gt; Organization &amp;gt; Team &amp;gt; Personal &amp;gt; No Standards“. It is that simple. Everyone has standards. However, some standards are more important than others. When developing your own standards you should consider those standards that are greater than you first. So your standards should extend those standards that are defined above your position.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 13:40:07 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725877</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://research.web2announcer.com/">research</category><category domain="http://standards.web2announcer.com/">standards</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Object Oriented Programming Is Your Foundation</title>
    <link>http://web2announcer.com/go/2725717</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Object Oriented Programming is going to be the foundation of everything we talk about from here on out. OOP provides huge power and flexibility later on down the line when we discuss techniques to help in the maintainability of our code.&amp;#xD;
&amp;#xD;
As a side note, you will find that I tote maintainability as a hugely important factor. To me, maintenence is the biggest comsumption of development resources whether it be through bug fixes or adding new features. Anything that can make code easier to maintain long term is, in my book, worth exploring.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 09:52:54 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725717</guid><category domain="http://net.web2announcer.com/">.net</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Creating custom PHPUnit assertions</title>
    <link>http://web2announcer.com/go/2725659</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    While developing PHP applications and applying developer testing the applications safety net will grow along the timeline, and as normal code, test code should be in a fresh, odour free state too. A common test code smell, amongst others, is the duplication of assertion logic which can reduce reusability, readability and thereby obscure the specific verification intention of tests. To subdue this special smell several patterns and refactorings are available to acquaint the test code with the DRY principle. So in this blog post I&#039;d like to set the focus on some of the aspects of the Custom Assertion pattern, by showing how to create custom PHPUnit assertions, which attacks the above mentioned smell and its retroactive effects with a huge antiperspirant flagon,  while also providing the chance to build a customer friendly and domain related test vocabulary.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 08:29:09 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725659</guid><category domain="http://frameworks.web2announcer.com/">frameworks</category><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://php.web2announcer.com/">php</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The Onion Architecture : Part 1</title>
    <link>http://web2announcer.com/go/2725630</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    I&#039;ve spoken several times about a specific type of architecture I call &quot;Onion Architecture&quot;.  I&#039;ve found that it leads to more maintainable applications since it emphasizes separation of concerns throughout the system.  I must set the context for the use of this architecture before proceeding.  This architecture is not appropriate for small websites.  It is appropriate for long-lived business applications as well as applications with complex behavior.  It emphasizes the use of interfaces for behavior contracts, and it forces the externalization of infrastructure.  The diagram you see here is a representation of traditional layered architecture.   This is the basic architecture I see most frequently used.  Each subsequent layer depends on the layers beneath it, and then every layer normally will depend on some common infrastructure and utility services.  The big drawback to this top-down layered architecture is the coupling that it creates.  Each layer is coupled to the layers below it, and each layer is often coupled to various infrastructure concerns.  However, without coupling, our systems wouldn&#039;t do anything useful, but this architecture creates unnecessary coupling.
	</content:encoded>
    <pubDate>Wed, 30 Jul 2008 07:31:03 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725630</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://trends.web2announcer.com/">trends</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Using Continuous Integration to Reduce Project Friction</title>
    <link>http://web2announcer.com/go/2725153</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Getting your team to adopt a Continuous Integration mindset will simplilfy deployment and result in faster projects and better code.
	</content:encoded>
    <pubDate>Tue, 29 Jul 2008 19:01:51 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725153</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Mock Objects - Faking real world processing</title>
    <link>http://web2announcer.com/go/2725069</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    To someone who is new to unit testing, the idea of mock objects can be confusing to say the least. In this tutorial, we will focus on the concept of mocking in general. What is a mock object? What is it used for? Why can&#039;t I mock object XYZ? Let&#039;s look into these questions and maybe clear a bit of the air on the use of mock objects.
	</content:encoded>
    <pubDate>Tue, 29 Jul 2008 17:04:40 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2725069</guid><category domain="http://how-to.web2announcer.com/">how-to</category><category domain="http://java.web2announcer.com/">java</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://tools.web2announcer.com/">tools</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>8 Reasons Why Model-Driven Approaches (will) Fail</title>
    <link>http://web2announcer.com/go/2724887</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    If you want to build model-driven software you’ll need to devise a methodology based on ideas and experiences from others. This article shares with us 8 gotchas of Model Driven Engineering.
	</content:encoded>
    <pubDate>Tue, 29 Jul 2008 12:54:29 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2724887</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://research.web2announcer.com/">research</category><category domain="http://standards.web2announcer.com/">standards</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Using Gist for Responsible Software Blogging</title>
    <link>http://web2announcer.com/go/2724353</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    GitHub unveils version controlled snippets. I take a look at them.
	</content:encoded>
    <pubDate>Mon, 28 Jul 2008 22:49:06 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2724353</guid><category domain="http://announcement.web2announcer.com/">announcement</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://ruby.web2announcer.com/">ruby</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>The lost art of user experience</title>
    <link>http://web2announcer.com/go/2723716</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    A web developer musings about his favorite part of the development process - user interaction design.
	</content:encoded>
    <pubDate>Mon, 28 Jul 2008 16:18:50 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2723716</guid><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://opinion.web2announcer.com/">opinion</category><category domain="http://usability.web2announcer.com/">usability</category><category domain="http://web-design.web2announcer.com/">web design</category><category domain="http://programming.web2announcer.com/">Programming</category></item><item>
	<title>Zend Framework Architecture</title>
    <link>http://web2announcer.com/go/2723620</link>
    <author>unknown@DZone.com</author>
    <content:encoded>
    Overview of the Zend Framework architecture and 3 graphs showing the level of coupling between components set at runtime.
	</content:encoded>
    <pubDate>Mon, 28 Jul 2008 14:56:52 GMT</pubDate>
    <guid isPermaLink="true">http://web2announcer.com/go/2723620</guid><category domain="http://frameworks.web2announcer.com/">frameworks</category><category domain="http://methodology.web2announcer.com/">methodology</category><category domain="http://open-source.web2announcer.com/">open source</category><category domain="http://php.web2announcer.com/">php</category><category domain="http://programming.web2announcer.com/">Programming</category></item></channel>
</rss>