> > Piotr, according to my calculations, on a ten hour working day, without > breaks that would be a compilation every two minutes or so. I think that > even with zero seconds compilation time I wouldn't manage that. I've always > been taught that the time between compilations is more important than > compilation time, so a "thinking/debugging/edit/compile" cycle that fits > into two minutes, concerns me. > > I used to work on systems with a 45 minutes build time between debugging > runs, so we would have been in heaven with ten seconds! > > My small point is that focussing on losing ten seconds per compile may not > be the place where you can make the most gains. Of course I might be wrong. > > Paul > >
Maybe I`m saing to much about compilation time, but I was thinking generally about the time that tools consume. So as I said - it`s the time eclipse needs to open a file (sometimes it hangs and opens a file in 10 seconds), the time to wait for code completition etc. The thinking/debugging/edit/compile cycle is different in different stages of programing, and sometimes I`m codding for an hour without compilation. Mostly during some debugging/testing process - this time is shorter and then compilation time is important. BTW. does flex supports some dynamic recompilation ? I mean - can I change the code during debugging ? I know that there is always a place to improve programming skills and organization - and thats a great subject for another discussions. How much code should be created during one iteration etc? For ex. when I`m adding a button that invokes some remote cairngorm command - I write in one iteration - Command class, new Event, Delegate function or new delegate etc. But during some interface improvements - like aranging items on form or aranging windows - I don`t see another solution than correct/recompile/test Do You have an application in FLEX that requires 45 minutes recompilation time ?? How much functionality can You add during one iteration ? Regards
