Over the next number of posts I am going to be exploring the world of design patterns. We’ll look at some of the most commonly used patterns and how they look in C#.

How can approach help a programmer to create better design and code? 13 rules of the pragmatic approach.

You're likely using somebody else's code so that you can Get Things Done. But what happens when you hit a snag? Say, for instance, the code isn't doing what you think it should; then what do you do? Advices from Matthew Weier O'Phinney.

I bet you could point to the weakest software developer in your department with little hesitation. But if I asked you to identify your criteria, it's unlikely that "metrics" would play any part in that judgment.

The reasons for that I believe are manifold but boil down to 1) Gain user feedback 2) Release early to gain "mindshare" and/or get first to market. 3) Your QA process or team isn't that great (or your unwilling to spend money on them) and you'd rather have users do your testing for you. 4) You need to gain the confidence of your customers / investors in what you're building.

Statistics about Wicket.

Within Project Management we use a lot of metrics. The metrics will provide some relatively objective "description" on how the project is doing. They are the Project Managers' seismometer, they record if your project world is rocking, and how hard. Traditionally our metrics are focused on time and money. But how about that all important resource, the developer?

If we want our customers to embrace Information architecture, we must help them understand why we need it. IA is about selling ideas effectively, designing with accuracy, and working with complex interactivity to guide different personas (potential customers) through website experiences.

How do development shops balance agility with governance? This post shares some best practices and invites people to a free webinar with a guest analyst from Forrester research to discuss in more detail.

Agile is here to stay. The economic difficulties of the past months have finally put waterfall out of its misery; now more than ever, long requirements phases and vaporous up-front documentation aren’t acceptable. Software must be visible and valuable from the start.

Doesn’t that title just get the blood pumping? Proof verification has a reputation for being an inordinately academic subject. In fact, even within scholarly (otherwise known as “unrealistically intelligent“) circles, the automated verification of proofs is known mainly as a complex, ugly and difficult task often not worth the effort. This is a shame really, because rigorous proofs are at the very core of both mathematics and computer science.

How to integrate a code generation utility to Maven's build lifecycle.

Functional programming languages have been gaining momentum provoking increased interest in power and flexibility they may provide. Johnatan Tang highlights, however, the flexibility vs. productivity tradeoff due, amongst other things, to the fact that object orientation makes organizing programs easier and more straightforward.

Bob Martin describes the core of BDD (Behaviour Driven Development) and shows how it closely parallels the way that we already describe finite state machines. In doing so he highlights new potentials in both.

Tried TDD and abandoned it the moment you've tried it on 'real' code? Learn how to tackle these 'hard-to-test' areas, that those presentations and introductory books just don't seem to explain well.

I really wanna do DDD. But I also got to thinking: “Why, actually?” The current architectures and approach to design with a services and dao layer many of us have in web-applications using either spring/hibernate or ejbs is "good enough", as in, it gets the job done fine. So, is the DDD movement mostly an intellectual exercise or does it really matter?

Frameworks are growing with every release. Classes are changed, removed and added. In this series I zoom in on some well known projects and analyze their class names with completely meaningless statistics. First: Spring 2.5.

After making allot of mistakes in the UML diagrams, reading books and taking feedbacks I was actually able to make some clear and more understandable of them. This was always a problem; to make it better one I always ended up in making it more complex.

Who make the best Scrum Masters? First off there are several roles that make a risky proposition for Scrum Master…

In this post I'll try to explain once again what is definition of done and why it's so important to have the same definition at least among all the people involved in the development of a single project.

Over the years design patterns are being best practiced in IT and SE. Design Patterns are the solution guidelines to common problems identified in the software applications. DP are taken care during application design or during refactor process. Most of the times DP are not followed because of lack of experience or knowledge. In case of MCV/MVP, lack of knowledge of difference between them is one of the fear factor not choosing the right pattern. This article would try to differentiate between the usage MVC and MVP.

Let's start with a fundamental question of "Why?". This question is so basic and simple, that it sometimes eludes many of us in our day-to-day work routines. So why bother with an agile process? It does not make you produce software faster - despite popular myth. It does not necessarily bring higher quality - at least not automatically. It does not let you work less hard - on the contrary, you are supposed to be an efficient long-distance runner. Why then? It all boils down to the fact that agile processes and practices let you deliver awesome software, much easier than any other processes.

A tip for people new to collections which use blocks for iteration (like Ruby does)

It is with great pleasure that I have been able to finally open-source the Guide to Writing Testable Code. I am including the first page here for you, but do come and check it out in detail.

Although test-driven development is now considered common sense in the OO world, it is very rare in database development. This session looks at the reasons behind that and presents solutions and best practices for test-driven database development.