You will be more efficient and get more done by not overworking. You need time away from thinking about something or you fry your brain so it's of no use to you. Take the weekend off to relax, recharge, and motivate yourself for the following week. Take a 5 minute break to get up and walk around once every 45 mins.
This is especially true in a concentration intensive job like game development.
This has been proven over time to achieve efficient results. There is a reason the average working week is 40 hours. If the final total is not something that you think you can achieve reduce the scale of your project and repeat the above process until you arrive at something manageable.ĭon't Overwork - a recommended work schedule. Even if you are very conservative in your estimates, almost everything is going to take longer than you expect, and you are going to run into endless jobs that you never predicted. Once you have your list, estimate how long each job in the list will take and write it next to it. We are not looking to list every minute detail here, just an overview of the big picture - each big job. Also, list all the essentials that every game needs eventually - things like save game functionality, a website, rebindable keys possibly.ĭo this in broad strokes. You may not even know how you will achieve them at this stage. List all the core features that your game will need.ĭon't detail how you will achieve them. If you don't have a schedule you will fumble around endlessly wasting time and never get the thing done.
Now that you have a decent prototype it's time to plan out in a very rough way your schedule for the project.
0 kommentar(er)
