Is it normal to work N days of work without writing a line of code?

Question

Career in IT

Let's take this situation: we work remotely, there is a list of tasks (without deadlines). There are no trackers that take screenshots from a computer every five minutes.

Tasks require understanding new technologies (framework\protocol, etc). You need to find a balance between doing "quickly" (taking a quick look at the documentation) and "qualitatively" (deeply delving into the topic).

Naturally, the company pays money for working functionality, and not self-learning.

Hence the question - is it normal for N days of work without a written line of code? With the condition that at that time the documentation was being read, "what is better" was being considered, and so on. If you are starting to work with a new technology, what is the normal N number for you?

Answer 1

The number of commits should not interest anyone at all. Everyone commits differently, someone pushes every line. Someone at the very end pushes one big commit.
Choose the style that you like best and meets your company's standards for assessing productivity.
In the end, it does not matter - if the task is completed on time and the quality is as expected.
PS There is one exception - when you work in a team that does a good code review - it makes sense to commit more often to get reviews and fix bugs faster.

Answer 2

Depends purely on your agreements with the employer

Answer 3

Naturally, the company pays money for working functionality, and not self-learning.

the company can think how it wants. Modern IT is a permanent process of learning. It is at a construction site that you can lay bricks without thinking, but here you can’t do without it.
There are two options:
1. The employer understands this and allows you to educate yourself, understanding the specifics of the field .
2. You fall short in terms of competence or your responsibilities are not clearly outlined and you are forced to spray.
Either way, it's all bad.