Jan Slodicka showed me a lot about Resco’s development machines and how the 4 programmers and the tester work together. (Talking about the Palm division only; Resco has more work force in PPC dpt. and on the enterprise projects.) Lets dive straight in by looking at the machine configurations!

Resco’s dev machines
Most of the people working at Resco’s are still using CRT’s – there seem to be rather few LCD’s here, and I saw no dual monitor workstations either. The machines themselves are of varied age, there seems to be a lot of classic Compaq hardware in use.

Resco’s Palm division uses Metrowerks CodeWarrior for development. CW is used even for the Symbian development. Desktop part is done using MS Visual C 6.0.
Metrowerks tools fit the bill very well and are more than comparable to the MS tools – apart from stability problems.
Jan has a habit of keeping feature lists, etc all in CodeWarrior(text files).

Bug tracking
A bug tracker was installed generally a few years ago, however, the developers never got accustomed to the system and fell back to using text files and Excel sheets. Their tester still uses the bug tracker occasionally.

Revision control
Revision control is handled by Microsoft SourceSafe. SourceSafe is in use at Resco’s for more than 10 years without any problems whatsoever – the merge difficulties are perfectly normal according to Jan.

Testing methodology
The developers do limited testing using both simulators and real devices. The tester works primarily with real devices. The Sinulator is used also for making screenshots. We had a photo of some of their testing devices in the first part of this series – look at them here!

Multiplatform strategy
Resco’s multiplatform strategy consists of rewriting the program for each operating system in a separate offer –common code base is small – low level libraries for imaging and zipping, desktop component for the Viewer and server components for the WorldCup application. No multiplatform-SDK’s are used for UI look reasons. (Jan says that this decision was taken because of past experience with multiplatform development for the desktop systems.)

Selection of applications
Resco strategy is to concentrate on a few strong titles created in a close co-operation with the user community. This demands heavy investments in the initial phase, but results in products with higher added value and longer life cycle.
Overall, I hope that you enjoyed this smorgasbord of interesting facts about Resco. I consider their development system very interesting and probably also very effective! Tune in soon for information on what Jan Slodicka thinks about the Palm OS economy(and its ESD’s).

What do you think?

Related posts:

  1. Resco releases Resco Suite for Palm OS
  2. Resco’s oppinion on platforms and sales
  3. Resco IDGuard will get a desktop component
  4. WebOS intro interview – Miro Pomsar, Resco
  5. Resco Explorer 2009 for Palm OS released!

2 Responses to “The Resco way of development”

  1. Very interesting! Thanks for reporting. I feel sorry for them using SourceSafe for that long but I guess they’re used to the pain by now.

  2. Hi Brennan,
    as said – they said that it is not problematic at all. Its probably like with Palms – either you get a lemon or not =).

    Best regards
    Tam Hanna

Leave a Reply



You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe without commenting

© 2013 TamsPalm - the Palm OS / web OS Blog Suffusion theme by Sayontan Sinha