Programming 24/7?

Question

Programming

Hello, I am a beginner student.
This is going to sound a bit strange, but I would like to know if it is possible to become a normal programmer without coding 24/7?
I like programming, even very much, you don’t think. I just sometimes want to take a break (sometimes watch TV shows, play games).
What did you do when you were a student and how did you manage your time?
Of course, I will devote most of my time to coding, but will I have free time to be lazy?
By nature, I’m generally a real sloth, but I’m also responsible, so I can’t waste all the time in vain.
Share your life experience in general
PS please do not write what you should think about another specialty. In this life, I can’t do anything except coding :(

Answer 1

Is it possible to become a normal programmer without coding 24/7?
1. coders code, programmers write programs
2. 24/7 only moronic shitcoders code
Summary: coding 24/7 you can only become a dumb shitcoder
coding But at the same time, do not forget about your studies. In short, look for the golden mean. Forget about "coding" in general.
person by nature. All mentally relatively healthy people are lazy by nature, but this does not mean that you have to lie on the couch near the TV around the clock.
I don’t write, but it’s always worth thinking about, including about another specialty

Answer 2

You need to work not for 12 hours a day, but with your head.

Answer 3

It's not about how much time you spend on "coding", but how much useful code and knowledge you can apply somewhere, because without seeing the results of your work, professional burnout begins. You can code shit 24/7, but you can’t write quality code. After 4 hours, your productivity will be somewhere around 30% of the original, after another 4 hours - 5%.

Answer 4

I remember writing my thesis, I just sat down and started coding, coding, coding (about 24/7 for a whole week) and I realized that the code is already huge, but there are no solutions: a lot of errors, unmeasured exception handling code ....
Well and when I just stopped and thought, I took out a summary, drew a finite state machine graph for my task and wrote the code that I needed in one evening.
Yes, then, after all, I did a little bit of error handling and other bindings, but the main code was created from the picture on a piece of paper (3 hours to draw the picture and a couple more hours of coding).
That's why I remembered it - because many tasks, in principle, cannot be solved by coding. You need to think with your head (on a piece of paper) first, and encode the already completed decision.
And there were many such examples in my not too programmer practice. As soon as you see that the project is falling asleep, you need to stop and rethink everything from the very beginning, and only then start work (perhaps from the very beginning).
But what is important to note is that sometimes, without going down the wrong path, you won’t understand which is actually the right one .... So, if you don’t know where to go, you can start with stupid coding (but realizing that it’s very likely that all this will into the urn).

Answer 5

Well, a student ...
Sleep, study, drink.
coding 24/7, I would say even worse, both for your personality in general and for your health.
Who's stopping you from sleeping 7-8 hours, studying/lecturing for 10 hours and watching TV shows or hanging out for 6-7 hours?