Jump to content

  • Log In with Google      Sign In   
  • Create Account

zee_ola05

Member Since 14 Mar 2010
Offline Last Active Dec 23 2014 01:35 PM

Posts I've Made

In Topic: Should I break_the_build?

25 June 2014 - 12:59 PM

Since this is related, I'd like to share the process we adapted in my previous work - Git Flow. This is a nice model to follow if we want our master/develop branch to be always working. It is pretty simple too.

 

http://nvie.com/posts/a-successful-git-branching-model/


In Topic: Noob question on hashmaps

24 June 2014 - 11:46 AM

Yes, Interface. :)


In Topic: Learning Game engine or Programming first

24 June 2014 - 11:43 AM

My apologies guys but i have 1 more question i didnt add here. 

 

Im currently reading a book that teaches you how to use C# in Unity 3d (so basically learning both concepts the same time). Seeing that unity 3d has more or less anything you require to make a fully functional game, do i really need to know how to WRITE code ? or just clearly understand what exactly the code is saying ? 

 

The reason im asking is because, while im reading this book and seeing examples... i had a lot of "ah-HA" moments and i fully understand whats going on so far(in relation to the example codes in the book)... but if i think of trying to write the whole code myself ... i just cant remember it...

 

I can see why writing code will be useful if something doesnt work out properly with unity but ill probably be able to google something specific.... so how important is it to actually learn how to WRITE the code? 

 

I think its good to know but not very important ... but im new to this and could be wrong 

 

Thanks a lot

You want to finish a game all by yourself with Unity? You will definitely have to learn how to code. Unity offers a great set of tools but you have to code to put them all together. If you're using GameMaker, then you probably won't need to code. But with Unity, I'm almost sure you will need it.


In Topic: Should I break_the_build?

24 June 2014 - 11:32 AM

 

"Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure." -- Martin Fowler (one of the small group of authors who put the term into popular use)

 

 

What do you call

If you are rewriting methods or rewriting your API, then that can break things.

 

Can't we call this refactoring too?

 

And I agree, we should refactor aggressively. smile.png

 

Redesign, maybe? I'm asking because I usually misuse the word "refactor" too.


In Topic: Should I break_the_build?

24 June 2014 - 11:29 AM

"Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves its internal structure." -- Martin Fowler (one of the small group of authors who put the term into popular use)

 

 

What do you call

If you are rewriting methods or rewriting your API, then that can break things.

 

Can't we call this refactoring too?

 

And I agree, we should refactor aggressively. :)


PARTNERS