Archive for the ‘SDLC’ Category

SVN client for Eclipse update

January 12, 2009

After updating the project from repository using Ant script (and upper version of svn client – 1.5), I came through the problem:

org.tigris.subversion.javahl.ClientException: svn: This client is too old to work with working copy XXXXX; please get a newer Subversion client

The cause is that svn client 1.5 changes the svn setup files so svn client 1.4 can not read them anymore. The remedy is installing new version of Subclipse plugin, here the process is described:
subclipse: Installation

Functionally complete

August 15, 2008

Functionally complete system is the one that covers all necessary operations for some activity.

Functionally complete system is the only one that allows you creating scalable software and not turn support into nightmare.

You need qualitative tertiary education to design functionally complete systems.

Why I like working for small companies

August 15, 2008

I like working for small companies because I love the dynamic environment there. Also can have there personalized relations, faster feedback and easy access to the one who makes the decisions.
In big company, manager is not interested in innovations and success, because it means changes for his cozy workplace. His salary is fixed and indexed, his bonus depends on how good he is in reporting. He has no any single reason for allowing me doing things in a better way, my way.
In small company, owner is interested in success a bit more. Sometimes he can be interested in success so much that even can take some risk hiring me 🙂

10 things you should do near the end of a project

May 20, 2008

When the project is about to be finished, some things do need to be done. This article from TechRepublic lists them so I won’t forget to do them at the end of my next project again 🙂

eXtreme Refactoring

April 11, 2008

There are lots of badly designed information systems crying for refactoring. But big bosses don’t want to spend money and time for it because of uncertain result. Refactoring needs a methodology clearly answering two questions:

1. Does it worth to perform the refactoring at all?


2. How much does it take (efforts, resources, etc.) ?

The methodology (or framework) should be as efficient and measurable as Agile for Software Development. Here is a link to the immortal article of Brian Button “Extreme” Refactoring — The Video Store Revisited