Path: chuka.playstation.co.uk!news From: "Peter" Newsgroups: scee.yaroze.freetalk.english Subject: Re: compile times... Date: Tue, 27 Feb 2001 01:34:02 -0000 Organization: PlayStation Net Yaroze (SCEE) Lines: 69 Message-ID: <97evv9$31k7@www.netyaroze-europe.com> References: <97eol8$31k5@www.netyaroze-europe.com> <97eqpv$31k6@www.netyaroze-europe.com> Reply-To: "Peter" NNTP-Posting-Host: host213-122-81-52.btinternet.com X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 I design most of my code up front using class diagrams and activity diagrams etc, so doing the actual coding is the easy bit. Its kind of like writing up an essay when you've written the notes already. I try to experiment as much as I can on paper first and maybe I'll write some code to keep me focused (generally this gets discarded but some-times I keep it). When I think I've got a fairly strong design I'll pick out some of the architecturally significant classes and make a start on these. If I'm coding a complex class then I'll implement a method and then test it using printf's etc but if its a simple class I'll write all the methods and then test it afterwards. Once these classes are out of the way I write whatever additional classes are required to implement an important use-case. Once this is all tested I move on to the next use-case and the next one and the next...you get the picture ;) I can't really be more specific about time though. Sometimes I'll go for an hour without compiling sometimes it will be every 10 seconds. It depends upon what stage I'm at and how much I've had to drink ;) Hugz, Pete "John ( QuietBloke )" wrote in message news:97eqpv$31k6@www.netyaroze-europe.com... > It depends what Im working on. At the early stages of development I will > write a discreet block of code and then wrap some code around it and test > in isolation using printfs where necessary to see my results. It probably > comes out to 30-45 mins thinking about it and coding.. of course then I > usually have to compile a few times to get rid of any stupid typo's.. if all > goes well then the testing only takes a few mins and I can remove the > printfs etc and move on. > Near project end its just a case of tweaking and the code changes are all > just a few lines generally.. 1 minute to code before I recompile again.. in > fact at that point I make the changes and compile faster than I can dowload > the new version to the Yaroze. > > > "Matt Verran" wrote in message > news:97eol8$31k5@www.netyaroze-europe.com... > > Here's a nice techie topic: > > > > I was just reading the latest issue of Edge, Gregg Barnett FAQ, and he > > mentions the time between between compiles being just an hour back in the > > 8bit days. I guess he's thinking of commercial projects with big teams, > but > > it's really rare for me to code for an hour without compiling and testing. > > I pretty much never go more than about 30 minutes without giving features > a > > little test of some kind. > > > > I was just wondering what everyone else's coding habits were, anyone code > > for hours on end so confident in their code they don't need to compile? > > > > > > > > MattV > > > > > >