| 1 |
* Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 2 |
|
| 3 |
> The only advice I've got is to do things in increments as small as |
| 4 |
> possible. Don't do "big bang" integration. Make sure there is a |
| 5 |
> runnable testable program after the first week of development. Maybe |
| 6 |
> it doesn't implement any significant features, but you must have |
| 7 |
> something runnable and testable at all times. Otherwise, you can get |
| 8 |
> too far down the wrong road before you finally figure out that either |
| 9 |
> a) what you specified isn't going to work, or b) they didn't |
| 10 |
> understand the specification at all. |
| 11 |
|
| 12 |
ACK. And another important tip: split your big problem into smaller |
| 13 |
and smaller generic sub-problems. Then you'll have great chance to |
| 14 |
reuse an existing package or let some contractor develop/adapt one |
| 15 |
without telling him about your actual project. |
| 16 |
|
| 17 |
Movie tip: "The Cube" ;-) |
| 18 |
|
| 19 |
|
| 20 |
cu |
| 21 |
-- |
| 22 |
---------------------------------------------------------------------- |
| 23 |
Enrico Weigelt, metux IT service -- http://www.metux.de/ |
| 24 |
|
| 25 |
phone: +49 36207 519931 email: weigelt@×××××.de |
| 26 |
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 |
| 27 |
---------------------------------------------------------------------- |
| 28 |
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme |
| 29 |
---------------------------------------------------------------------- |
Archives