True, but that's the way it is - writing comments takes time and effort (especially if you try to do it right). But it's an effort that is supposed to pay off, when you come back to code you haven't taken a look at for a long time, or when others have to work with your code and try to understand what strange things were going on in your mind when you wrote itCjkjvfnby wrote:IMHO you do duoble work on writting and supporting code. You write code in two langages (english and python).
Also true, again but: Knowing me, if I don't add the comments immediately, I'll never do it. And even if, I'll probably get around to it so much later, that I'd need the comments already in place to understand what I'v been thinking when writing all that crapMay be you can make verbose implementation later, after finish some stage. This has one big benifit: after some time you will review you code again, and may found some issues.
Everyone has his own style/preferences how to do that, I guess. See milesers reply. Also an interesting approach, but if I did it his way, I'd probably never get past producing a lot of comments...