Jump to content

  • Log In with Google      Sign In   
  • Create Account


agentleo

Member Since 10 May 2010
Offline Last Active Jul 01 2014 06:26 PM
-----

Topics I've Started

Recommendation for a junior generalist / gameplay programmer portfolio

03 February 2014 - 01:04 AM

I am currently in process of reorganizing my portfolio site  as I am looking to get into a junior generalist or gameplay programmer position and I am curious to what are some of the key programming techniques , or examples recruiters would be interesting in seeing.  To give a little background info I am a mid twenty's new grad B.S Software Engineering student looking for my first full time job in the industry.  I have 5+ years work experience outside  of the industry working in technical positions , (so I am experience working in a professional environment, but as far as industry cred I know this may mean little if anything at all. ). Currently I plan to have a few tech DirectX level demo's showing off various  rendering techniques for a side project game engine I am working on for experience. I also plan to have a  full space shooter clone game with all  the bells and whistle ( menu's, highscores, etc). All these will be done in C++ except for maybe a C# demo I may throw in to display my actionscript 3.0 skillset  with Unity Scaleform integration. I have more older projects I can use but I want to show off what my current skillset is, not what I have done in the past so I am going for a quality over quantity approach so I want to limit my portfolio  to a best of.  Any suggestions would be appreciated and if you have any leads that will be out at GDC this year I would definitely love to talk more.


C# composition issue

14 May 2012 - 11:29 PM

Hello, I am looking for suggestion on a comosition pattern for a recent C# project I started working on . I am an experience c++, java programer, so I am not exactly new to programming, just newer to c#. I believe I gotten to a good start but I just looking for recommendation to see if I can improve this . object owns the componets. the componet class will act as a base class for various componet interfaces. I have not created the interfaces yet.

Object class
code
using System;
using System.Collections.Generic;


public class Object: IDisposable
{
  #region Fields
  
  

  
  
  //private
  
  private IList<Componet> componets = new List<Componet>();
  #endregion Fields


  public void AddComponet(string componetName)
  {
   componets.Add( new Componet( this, componetName));
  
  }
  
  // public
  
  public void Dispose()
  {
   foreach ( var componet in Componets)
   {
	componet.Dispose();
	
   }
  }


}
}


Componet class
using System.Collections.Generic;

namespace Engine
{
public class Componet: IDisposable
{
  private string componetName;
  private Object obj;
  //public IList<
  
  
  
  internal Componet ()
  {
   this.obj =obj;
   this.componetName= componetName;
  }
  
  
  
  
  public void Dispose()
  {
	
  }
}
}






PARTNERS