> And then just get sleepy when I do start reading code. Could it be that the code you are looking at is solving a problem that is entirely uncompelling to you

> And then just get sleepy when I do start reading code. Could it be that the code you are looking at is solving a problem that is entirely uncompelling to you? In my estimation, I got better at programming by trying to solve challenging, real-world problems rather than by laser-focusing on specific blocks of code or documentation. Most of my time these days isn't even writing code. It's thinking about how to solve the problem abstractly. If you are trying to solve some problem in your head, it really helps if you find parts of it exciting or enjoyable. You can very quickly spot a developer who is not interested in their problem domain. They are typically off in some devops Narnia constructing a matrix of new problems that are interesting to hide inside of.