Friday, 21 December 2012

Lotus Notism #47 - Cant archive when over disk quota!




I am "over disk quota" in lotus notes, so I go to "archive" and this is what I get! 

Monday, 17 November 2008

Don't Do This

Here's a little list I compiled on a recent project, some tips to follow, a kinda mantra for simple-stupid software development:

DON’T DO THIS:

- Performance Test without a performance testing environment

- “Ego engineering”

- Use :

o Synchronize

o Static

o Global Variables

o The “coat-hanger”

- Over engineer

- Pre-empt performance optimizations

- Work without requirements

- Change technologies (mid-stream)

- Skip regression testing

- Test – if you are a :

o BA

o Developer

- Do things you aren’t qualified for

- Re-invent the wheel

- Assume anything

Friday, 7 December 2007

Names matter

Names matter in many domains and many ways. People like to be referred to by their name, not a number, or some generic term like "mate" or "buddy". Our name identifies who we are as an individual. In the "olden days" our surnames (at least in the Western world) were often derived from what we did as a profession (e.g. Smith, Baker, etc) . It's not that different in the coding world, names identify the purpose of an entity, what it does, what it's for, why it exists. At least they should.

Many developers do not take the time to think about what their interface, class or method is and will be for, and hence name it appropriately. A generic name like "MyClass" simply means we (any one else in world other than the author) have to read the documentation (if there is any) or the code itself, just to get a feel for what it does. And using uncommon terms and abbreviations doesn't help either. All this wastes time, everyone's time, even the author's himself after some time has gone by.

Providing a name that matches the purpose is mantra of Java, and it should be for all coding. In fact it can be applied much wider than just Java code, what about HTML pages, and documents (yes .xls and .docs), and don't forget packages and directories. I'm not going to provide specific details on naming conventions or formats here, they are included in most standards and guidelines out there.

It is also important to re-name (or refactor) entities when their meaning changes. Or provide a new one (perhaps a sub or super-class of the existing one) with a name that fits better for a new variation. In Java you can even keep the old name as a unchanged sub-class of the new name, and "deprecate" that old class.

Saturday, 15 September 2007

I found this page which lists "all" you can do with microsoft windows/dos batch file redirection. It does not have totally clear descriptions, but it's not bad. One redirect which is useful is

Duplicating handles
The & redirection operator duplicates output or input from one specified handle to another specified handle. For example, to send dir output to File.txt and send the error output to File.txt, type:
dir>c:\file.txt 2>&1

or

To find File.txt, and then redirect handle 1 (that is, STDOUT) and handle 2 (that is, STDERR) to the Search.txt, type:
findfile file.txt>search.txt 2<&1

Tuesday, 16 January 2007


In response to an article at The Age iPhone skins irk Apple I have found an updated version bearing in mind copyright concerns: