It is possible to write software that solves real business problems, cheaply and reliably. The recipe is well known, even though it's not easy to do.
I am a software developer. I'm happy to work as a programmer for ThoughtWorks, mostly in the Milano area. I teach at the Università dell'Insubria.
Working with me: if you're a computing student, you may do an internship with one of my (former) clients. If you are a developer interested in working in a team that does Extreme Programming, send me your CV.
On Thu, Jul 23, 2015 at 1:29 AM, John Carter john.carter@... [extremeprogramming] <email@example.com> wrote:
Now the Absolute Number One enemy of a successful refactoring is change sprawl. [...]
In my experience, the number one enemy of successful refactoring is that we make the code worse when we refactor. We create abstractions that are not right and make the code more complicated. We introduce coupling in the name of removing duplication. We can't tell the difference between "simple" and "easy". We add yet another framework. We hide interactions in global variables (or static methods and fields, which is the same) and we delude ourselves it's elegant code. I don't know, and I don't even mean that the problems I described apply in your case. I simply point out what I have seen, many many times.xpmatteo