Re: When to stop reading and start programming?

["Steve" <nospam_steved94@comcast.net>]

"Freejack" <freejack@nowhere.net> wrote in message 
news:pan.2005.10.28.12.49.52.666403@nowhere.net...
> Recently I've begun a foray into the art of Region Based memory
> management. Specifically with the intent of creating a working
> library for Ada development. Naturally it's a good idea to look into what
> others have done before me.
> There are a bunch of academic papers on this. Mostly centered around ML
> Kit or Prolog systems.
> It's become abundantly clear that Ada provides more than enough Type
> information to make this work.
>
> However, how many academic papers should one wade through before actually
> getting started on the code? Heh. Should I wait for my eyes to start
> bugging out of my head?
>
> Any tips from the more experienced among us?

Always start with a plan.
Put together a document that describes what the system will do.
Include diagrams on how the system will do it.
Include a description of how you will verify the system.

Once you have a clear understanding of what you're going to do and how 
you're going to do it, then it's time to start thinking about coding.

There are may methods techniques for making a plan, formal and unformal, you 
may just make your own, but use one.

Steve
(The Duck)

>
> Freejack