I was thinking 16 hours a day would be good ,how long do you guys sit down and learn. I said 16 because an older freind of mine said the longer everyday the better and quicker you become.
I highly recommend taking your time. You’ll get far better results being well-rested than simply throwing hours at the task.
4 Likes
How long do you learn code everyday?
Longer everyday the quicker you’ll burn out.
10-12 max.
1 Like
That sound like a good number.
Most of my initial learning took place during my middle- and high-school years. Typically this consisted of a mix of research (books and IDE help files) and writing code (any and everything that came to mind). If I had to guess I spent about two hours a day during weekdays and likely double that during the weekends.
At this point, nearly twenty years after starting to learn, I almost always learn as I go. Very rarely will I sit down and spend time learning for the sake of learning. Usually this is when I’m picking up a new engine and even then I don’t spend more than a few hours a day on learning.
6 Likes
Thanks guys I think ill study 10 hrs a day and see how that goes I just want to hurry up and make a game.
I did 15 hours on Saturday after a full week working, towards the end I was just sat there like a potato… Needed a couple of days for my brain to re-align (so it worked against me), treat it like a job do 8 - 9 hours a day and then shut it down / get off the laptop whilst taking regular breaks (for your eyes sake if nothing else).
You need proper food for energy, you should exercise and get plenty of sleep.
If your brain and body are functioning at an optimal rate, you can achieve more in 2 hours than you can in 20 otherwise.
7 Likes
Thanks guys:)
1 Like
You’ll notice it when the well has dried up.
2 Likes
I would say spend 2 hours a day learning new concepts, and the rest of the day practicing what you already know and applying the new concepts you learned that day.
Think of little scenarios where you can apply what you’ve learnt, and apply it.
If you’re just ‘learning’ all the time, and not applying and practising, you’ll forget what you learnt very quickly.
7 Likes
Learn and study while you are learning. As soon as you stop learning, walk away and do something else. Come back in an hour or after a good nights sleep.
Learning is a different process from working. Just throwing more hours at it won’t work. Your brain needs time to digest what it’s learned, to make connections. Learning doesn’t just happen by cramming in infomation. Most of the ‘click’ moments will come after you walk away.
If you need a number for hours I would say 2-3 a day. But really just keep going while you are enjoying it and learning efficiently. Some days that will be hours upon hours. Other days it might be measured in minutes.
5 Likes
You should have tried 16 hours before asking to understand what you just said. [people work 8 hours and return home exhausted]
Don’t get frustrated.
Yup. If you get stuck, it means you are about to learn something.
As long as you don’t stay stuck of course.
Any more than 3.14 hours per day exposes users to Dopefish syndrome wherein learning is intensely onerous.
Anyone that can go 6 hours or more a day and stick with it is either a psychopath or some sort of genius. When I started out, I could only handle a couple hours at a time before my brain would just start tingling and become less effective. Even now, when I’m focusing on a new language or framework at work, I max out after 5 hours or so. And I can’t do that every day, either.
I’d recommend 2-3 hours tops per session. Take a break afterwards and do something mindless like housework or watching a Michael Bay film. During that time, think over what you learned and relate it to your goal (I’m assuming, in this case, to make a game). If you have the energy, go back for another session, but stick to the same or closely related subject or reviewing stuff you went over earlier.
You’ll have many more 'Eureka, I finally get it!’ moments this way, rather than ‘WTF did I just read and how many times did I read that already?’.
1 Like
16 hours a day is unreasonable. IMO, 10 hours a day is also pretty unrealistic.
you can’t force learn anything. there will be times where you get stuck. for me, it was those times i had to put it down or do something else. when i came back, boom, solved it. (*a Eureka moment, as mentioned above).
with that said, if you’re making progress and everything starts to click and you want to keep going, there is no reason to stop. Your breaks and stop points should be controlled by energy and frustration level. So if everything is confusing, and nothing is working. time for a break.
Back when I had a lot more time I’d often spend 12 hours or more learning per day. I could do that for a few days or maybe a week. Then needed a break. I’d just try what some of the others have said. Put in as much time as you can. When you are feeling like you need a break. Take a break. Everyone is different. Certainly if you are feeling refreshed and absorbing information easily it’d be silly to stop just because your 2 to 3 hours of time for the day are up.
3 Likes
I was going to say this. I can code decent enough, but I want to learn some of the deeper stuff with making games, so what I have been doing is splitting my day up with different tasks, and one of those is just 2 hours of learning. But on the same days, I am also making progress on my game by doing some art and world building, and coding the stuff I know how to do correctly. I would definitely recommend that you don´t study 10 hrs a day, that is unsustainable for most people if it is pure learning… instead, get your feet wet in Unity at the same time doing stuff you know how to do already.
I probably get to do 4-6 hours per day Fri-Sun and 2 hours per day Mon-Thurs
I typically sit down with a goal in mind and when I complete that goal I take a break to process everything. While driving home or doing anything, I am processing and planning stuff in my mind. Drives me crazy that I can’t sit down and work on it for more hours.
I would probably do 6-10 hours per day if I could.
Learn it, write it on paper. If you think you know something or how to write code after you learn it, write a program on paper and after write the exact thing on a script, compile it and see how many error’s you get 
Now a days I spend most my time processing in my brain what and how I want to program and rethink it everytime on betters ways of doing it before I actually end up programming it. Once I get it figured out in my brain its crazy programming time!