PUBLIC MARKS from mbertier with tag dev

So, my point is that it is not the marketing of a product that counts — indeed, false marketing statements or tactics can backfire quickly. What counts is the product itself. Marketing should be the function of promoting the innovative advantages of a product in the above three categories.

This set of tools could be used to check InnoDB tablespaces and to recover data from damaged tablespaces or from dropped/truncated InnoDB tables.

Ironically, it’s usually easier to reuse publicly-available libraries (e.g. open-source libs on sourceforge) and public web services than those in the same company. The following things make reuse more digestible in an enterprise setting:

Subversion™ is the fastest growing version control system for distributed development teams and its rapid adoption is a phenomenon in small and large organizations. Recently evaluated to be the Sole Leader among Standalone SCM Solutions by Forrester Research, it is taking the developer world by storm. During this webcast, you will learn about the exciting new features coming out in the next release, Subversion 1.5, including merge tracking. Learn how to implement branching strategies that best fit your organization, and utilize merge tracking functionality to integrate changes. Learn from real life examples of branching and merging, so that you can accelerate development within your enterprise using Subversion’s new features.

There is a giant sucking sound of processing power, time, money, and intellectual resources being used up on this problem, all because someone wants to store a shopping cart in HttpSession.

Subversion 1.5 will support Merge Tracking.

Running phpunit --group bug42 AllTests.php will run only the tests associated with bug #42, regardless of what files and groups those test methods span.

This sounds funny, but some open source projects forget that they need users.

Passwords can be made both highly secure and user-friendly.

Well. As of version 3.2, PHPUnit will not only be able to calculate and collect a variety of software metrics. It will also be able to report violations of rules that are based on these metrics in PMD's XML format. This information can then be fed to any tool that integrates with PMD.

The talk covers many different aspects in API design and contains examples of good practice and common mistakes. Many of the principles and guidelines discussed aren’t new, but you rarely see so many of them summarized.

Beauty and The Beast. I begin my exploration of ugliness in code with some background and an overview of what most people consider to be crappy code.

In this paper, we provide a new two­fold solution – automated merging of changes that are done by a software provider after installation and manual merging of changes performed by the user thereafter. While some manual intervention is required in this approach, it is a more reliable solution. This approach also includes a tool to ease the manual file comparison and merge process.

Do you have an error message from your application? Then find the answer with Error Buddy. You can search over 40000 source code files and troubleshooting documents using our beta lucene/nutch search interface or if you prefer, search as normal using google. With LXR technology you can drill right down into the line of source code where it came from with full cross-referencing.

Jeff Attwood recently pointed out the difference between Gamma et al’s Design Patterns and Alexanders’ equivalent and outlined a critique of the former which characterises it as “replacing actual thought and insight with a plodding, mindless, cut-and-paste code generation template mentality”.

Submitting patches to Open Source code doesn't come naturally to everyone.

For too long, code reviews have been too much of a chore. This is largely due to the lack of quality tools available, leaving developers to resort to e-mail and bug tracker-based solutions. At VMware, we've traditionally done code reviews over e-mail. A significant amount of time was wasted in forming review requests, switching between the diff and the e-mail, and trying to understand what parts of the code the reviewer was referring to. We decided to fix all that.

it started out simple, but grew to be pretty powerful and useful quickly. It was designed to automate and simplify the process of creating review requests and actually reviewing code.

Asshole Driven development (ADD) - Any team where the biggest jerk makes all the big decisions is asshole driven development. All wisdom, logic or process goes out the window when Mr. Asshole is in the room, doing whatever idiotic, selfish thing he thinks is best. There may rules and processes, but Mr. A breaks them and people follow anyway.

Recently I began to write a paper on TDD Anti-Patterns, and decided to first quickly jot down some of the most common ones that others or myself have encountered “in the wild.”

Should you throw an exception, or return null? Should you use checked or unchecked exceptions? For many novice to mid-level developers, exception handling tends to be an afterthought. Their typical pattern is usually a simple try/catch/printStackTrace(). When they try to get more creative, they usually stumble into one or more common exception handling antipatterns.

Behaviour-Driven Development (BDD) is an evolution in the thinking behind TestDrivenDevelopment and AcceptanceTestDrivenPlanning.