Jump to content
  • Advertisement


  • Content count

  • Joined

  • Last visited

Community Reputation

531 Good

About ZeroBeat

  • Rank

Personal Information

  • Interests
  1. I have always been interested how companies work, especially game development businesses. My dream job was to work in the financial department of some game development company. As I was growing up, I played around with Delphi Pascal and 3d Studio Max, HTML, but I didn’t really make anything substantial, just really basic stuff... It was just something I did for fun after school/college.   So yeah, I studied Financial Economics in university (with the idea of being an accountant). After, I spent a summer learning C++ and then did Masters in Business Information Systems. During that time I found about this site. It really helped me with some of my projects even though they were not game related.   Afterwards, I realized that I want to make one game. However this “dream” game seemed something impossible for me. I had to become a much more productive and knowledgeable person to be able to make it. (Something between Castle Story and Stonehearth) So I joined my small family business. We needed a website, so I made one. Then I started to sell online (eBay, Amazon, my own site). From time to time, I make my own websites/tools to help me out.     All of this so that I can made my dream game someday. Well it’s been 4.5 years since having my idea. I failed to make my dream game 2 times now. However I did make a complete 2D space shooting game. Now trying to make it as a releasable product.
  2. ZeroBeat

    Questions for all programmers.

    1) What was the first programming language you studied? Visual Basic 5 or 6.   2) Did you have any Computer Science background before your first language (ie: boolean algebra, memory organisation, algorithms)? No.   3) The first language you studied was it self-taught, formal instruction, or both? Self taught. I was 10 or 11, my parents bougth me a book I could follow.   4) Was the Computer-Science background self-taught, formal instruction, or both? Mostly self-taught.   5) When you started to study Computer Science did it help your understanding of the language you first learned? Yes.   6) What kind of environment did you first program in (ie: the IDE or text editor, and the OS)? Windows 95/98 or 2000... Not sure what the editor for Visual Basic was called...
  3. ZeroBeat

    Is Programming Fun or Work for you?

    Overall I find programming fun. This is something that I always knew I will be doing....It can be really tedious or challenging at times. But after that, it feels very rewarding to complete those tasks!    I learned programming as I wanted to understand how games are made and how game companies work. Its very enjoyable to research different ideas, technologies. Gradually, I starting making small demos to see how scripting, networking, etc. works. It feels really great to create something and to reach a set goal. I don’t find it fun to program for the sake of programming. Like everything I guess, the process is much more rewarding if there is a goal to be reached.   At work, I use my knowledge to make our website and some other tools. As I can see how my contribution has a positive effect on our company, it feels really amazing. To admit, Its probably more "fun" at work as other people are also affected by my hard work. It makes it even more rewarding.
  4. ZeroBeat

    How did you learn C++?

    I bought Sam's Teach Yourself C++ in 24 hours. Probably it wasnt the best book..... (It was the only available book in the shop). With it and xoax.net (video tutorials), I was finaly able to compile and run my applications.   I used the lessons to learn how to program and then I would apply my new knowledge by building something small.  As I got more confident, I started making my own text based games. The book became a reference when I got stuck.   Like Kimmi said, its much better to learn something by appling the knowledge to a project. Start small with console based applications to concentrate more on the standard library and the languange.
  5. Motivation is a very personal thing and when you do something for the fist time its always the harderst! Also I think that disciple is important when programming even if a bit overlooked when programming is a hobby.... This article should be quite relevant: http://www.gamedev.net/page/resources/_/business/production-and-management/overcoming-procrastination-r3261   By trying to understand yourself and what makes you tick, its possible to improve yourself. For example, scratching done tasks gives you motivation. So writing what you need to do and trying to get more things off the list would make you feel like there is some progress being done. Hopefully this confidence boost will feed it self so that you work more.   By knowing what makes you tick, such as watching something or listening to some music, (hopefully) you can pick yourself up when you feel low and get something done.   Also like others before have said, having a list of pre-defined tasks helps a lot. I guess its because the problem(s) that need to be solved are already set. So rather than spending 10/20 minutes thinking what to do, I can straight away get working. More gets done = more happiness = more motivation to continue.   Here is a nice video which kinda picks some important parts: http://vimeo.com/24715531       edit: Failure, even if its demotivating is very important. Generally humans learn by trying things out and experiencing them. So even if you tried your best on a project and it didn't work out: The architecture was awful.... it took you ages to add new parts to the project.... The main part is that you worked on it and (hopefully) tried your best.   Its not easy to realise how much you will have learned from the experience. So that next time when you try to do this, you will have an idea how to make it work better. Maybe even you will try to apply the newly learned lessons to the project and re-factor it and cantinue until the next problem. Hence why, starting small and progressively working on larger projects is preferred.
  6. Doing something for the first time is always the hardest. Hence no amount of planning can trully prepare the developer for a solution to the problem.    Planing/Design is a very subjective thing. Sometimes just writing prototype code to see if a design works, can lead to understanding the problem better.  Rather than having talks with people of what could be and what not.   Sometimes there will be a lead designer/programmer who will decide how things will work..... Some people are very visual, some are less.. so some tools for planning will not be equally effective to get the point accross the whole team.   Its really dependents on the team of individuals and how their work well together.  Once one member wrote a design in psuedo code and I just expanded it while he was expaining to me what he wanted the code to do.   Sometimes a whole task is given to an individual with pre-defined list of tasks the code needs to do. eg write the whole MySQL code to get the data from a database.   I guess what I am trying to say is, as soon as possible try to get some experiance working with other people and you will understand .
  • Advertisement

Important Information

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

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!