Advertisement Jump to content
Sign in to follow this  
fir

broad phase and narrow phase

This topic is 1781 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Im curious if someone noticed the thing closed to my own view on

things: When i am working on programming (and i do it last 5 years

consecutive) i notice that i got two phases in it 

 

- broad phase - when i do general learning on many different thing 

(opengl, opencl, assembly, raytracing, optymization, rasterization... etc almost countles number of topics) -- it is very time consuming

 

- narrow phase - when i focus on my own code testing and experimenting

 

I noticed that broad phase consumes me a very large amount of time,

when i was more newbie I was doing more narrow phase coding (though my knowledge was more 'narrow'), recently really the broad phase things consumes

me rally over 90% of time (and sometimes i feel an urge to convince myself

to stop learning and go more with my hands into code 

 

Have somebody some opinions on that ?

 

 

Share this post


Link to post
Share on other sites
Advertisement


- broad phase - when i do general learning on many different thing
- narrow phase - when i focus on my own code testing and experimenting

 

What you're talking about is

- research

- and development

Often called "R&D."  Actually, "experimenting" (which you included in your "narrow phase") is part of "research." 

Every project inevitably involves some research, whether or not it precedes development (it may precede a particular task in the development process).

Many people use an iterative process that includes "experimenting" as you describe.

Share this post


Link to post
Share on other sites

 


- broad phase - when i do general learning on many different thing
- narrow phase - when i focus on my own code testing and experimenting

 

What you're talking about is

- research

- and development

Often called "R&D."  Actually, "experimenting" (which you included in your "narrow phase") is part of "research." 

Every project inevitably involves some research, whether or not it precedes development (it may precede a particular task in the development process).

Many people use an iterative process that includes "experimenting" as you describe.

 

I would call experimenting narrow phase - this is becouse for me every code writing is experimenting (I got no way to be sure how the thing
Im trying to do will really work/ look like)
Narrow phase is just coding (some project), broad phase is general learning.
As to research: broad phase (the thing i call it this name) is not really needed strictly for the project, but this is needed to be considered a reasonable programmer (todays programmers are expected to know broad scope of topics)

Share this post


Link to post
Share on other sites

Hi,

 

 

"Research is the intellectual backbone of game development...," found in  my signature below here. Research goes through phases, but in my opinion it should be according to needs and purposes for the most part. In other words, it should mostly be tied directly to what you need to learn for your current and near future game development processes. I will even go so far as to say that as you gain experience, then it will also be tied to both your source control and your  version control systems in the form of documentation, especially that which relates to the coding at hand.

 

What I am writing here is for anybody intending to have long term success in game development with the most efficient progress, but people who only do this as a hobby should focus on the things that bring them pleasure. Documentation is important for both philosophies of professional and hobbyist, however it is critical for professionals in regard to research that research documentation be directly connected in the development software to the coding. This serves many purposes as you can probably already imagine.  A major benefit to documenting your research is that it holds you more accountable to not wander too much in your research, since you will tend to always be reminded everyday of the ultimate objective of your research, thus not "waste any time" with bunny trails.  Some wandering is going to happen naturally because curiosity is too powerful to prevent all of the time, yet I believe that some benefit of learning for the future is to be had with it.

 

The more needs that you have in game development, then the more that you will see the logic of what I wrote here.

Edited by 3Ddreamer

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!