Shameer Subedar

Hi all,

I was wondering what people are using for their cruise control desktop monitor for java. I have previously used the CruiseControl.NET ccTray and that was great.

I have also read that you can configure CruiseControl.NET for java builds ?

Any thoughts and recommendations would much appreciated.

Thanks,
Shameer

Hi all,

I just wondering of the performance implications of using the auto boxing features. Does it matter if we allow the complier to put the smarts in or should we explicitly do the conversions ourselves ?

I am developing a real-time trading application and performance related issues are very important to us.

On a side note, having read an article in context of C# in regards to auto-boxing, they mentioned not to over use it as it may have performance issues.

Thanks in advance,
Shameer

You get the runtime exception because Base never implements the Observer interface. This won't complain at compile time as we are allowed to cast objects to any Interface type, this allows subclass of base to implement other interface(s) (if need)

However you can use the instanceof operator to check the runtime type of the object before you apply any cast.

Hope this helps,
Shameer

I found it to be an excellent book and good reference for later uses, note it is for SCJP 1.4 version of the exam

If the position is in the Finance sector you should be aiming for a base (min) $95k and much higher if it is an investment bank.

If you are not on a 457 visa and are a PR or citzen you shouldn't have any problems.

Hope it helps,
Shameer

If the position is in the Finance sector you should be aiming for a base (min) $95k and much higher if it is an investment bank.

If you are not on a 457 visa and are a PR or citzen you shouldn't have any problems.

Hope it helps,
Shameer

The Rational tool (XDE developer) does all and more. As do your design you can sync it up with your code and vice-versa. However its not a cheap tool. There are plugins for both Java and .NET.

My favorate is generating sequence diagrams on the fly as you are executing code.

XDE Developer

1. What is an avg salary for a person with 7 yrs exp in java, looking for a position as an Architect/Team Leader/Senior Developer etc..

Check some job agencies websites and they give average salary etc. For a senior developer to architect the range would from $80k - $150.

2. What are the cities that I should look for, what abt Melbourne ?

In general Sydney is the where most of the banking and finance jobs are. Melbourne is mostly engineering jobs. Brisbane and Canberra are doing well at the moment, mostly government jobs.

3. Cost of living(with family) ?

If you live in Sydney, it not the cheapest state. I heard recently the median cost of rent is around $300 a week; house prices are around $350k-$450k, if you want something nice maybe above $500k; fuel price is around $1.30 - $1.50 a litre. In general things are going up not down.

4. Approx what % of salary is taxed ?

Have a look at the ato website to give you details on the specific tax rates
ATO . In general you should be taxed around 40%, unless you earn above 150k you will be taxed 45%

Hope it helps,
Shameer

Go to IT Seek, and do a filter on your search criteria.

Hope it helps,
Shameer

I have found Craig Larman's Book very useful in UML and OO concepts.

Link

Hope it helps,
Shameer

Have a look at Cetus Links:

links.Cetus Links

Hope it helps,
Shameer

Due to my constraints I would like more people to peer review my work. So yes, the co-worker option as an immediate affect and helps meet the deadline(s).

However, if the process was formal, metrics could be collected, knowledge spread to other team members, technical skill learned from reading other peoples code etc. I believe this has more benefits to the team/company.

IMO, I would agree and prefer a Fagan style inspection, if customized to your needs it would provide more benefits in the long run.

This is all based on my experience and would like to know what other people employ in regards to code reviews. The most important factor in both processes is that that the correct people are involved and have the correct attitude towards code reviews/inspections. People do play a big part in both processes

[ May 16, 2006: Message edited by: Shameer Subedar ]
[ May 16, 2006: Message edited by: Shameer Subedar ]

Lasse, when I was working with Motorola they had a detailed Software Production Process and code reviews was one of the processes. Initially we had formal code reviews and informal code reviews. This was changed before we went for a CMM assessment and we only had formal code reviews.

Basically, informal code reviews were ad-hoc in that Tech lead or someone senior would review the code of a junior engineer. I had no issues with this and thought it was good as Tech lead pointed things out and was not intermediating as a formal review with 3 or more people.

The Formal reviews were based on the Fagan style, which included about 7 phases. The reviews were called inspections as this process was applied to any software artefact that was produced.
1. Planning - set a time in the schedule with PM
2. Inspection kit - author checks code, code is labelled etc and sends details to reviewers
3. Overview - given by author to reviewers
4. Preparation - individuals review on there own
5. Inspection - all meet and discuss the artefact
6. Rework/moderator check
7. Process improvement (optional if we went over/under the control limits)

In addition, the process was modified that defects were captured and analysed with ODC (Orthogonal Defect Classification)

In the main, I found this process very useful in detecting defects. The main benefits were IMO:
- Bringing new developers up to seed on company coding standards and introducing them to the business rules.
- More than one person inspecting the code, many minds are always better than one and you get a good result when everyone is focussed and have prepared for the inspection.
- Collection of metrics, very useful in seeing trends and common errors that are made.

Major disadvantages are:
- Control limits if you go over and under them, management then ask questions. For example you inspected 250 LOC of code in half an hour, not the prescribed 2 hours. A justification may then be required.
- Can be a very long process if there small change in code < 20 LOC

Having moved on from the tech sector to the finance sector, code reviews are very ad-hoc and it all depends on the team leader and type they want. In general it just one person who looks at the code, mostly the team lead. They spend at max about 10-20 minutes. These types of reviews don't provide much benefit because the team lead does not always know specific business rule, hence if there are errors it doesn't get picked up and just gets raised as a defect.

A practise that I employee is get a fellow team member that is familiar with code/business rules and get him to review the code at my desk. I generally walk through the code with him and let them ask question why this done etc. I have found this very effective as this does pick defects or incorrect business logic.

In summary, getting people together that are familiar with the code, business rules and with the correct attitude will make a code review/inspection very beneficial in improving the quality of the code..

You may Mr Fagan article useful.



Hope this helps,
Shameer

Hi Folks,

I was wondering is it possible to purchase HFSJ in an ebook format?

Many thanks,
Shameer