I find that coding while high never produces good code. I've done it before, and while I can sit and code for a long time, I just make too many stupid mistakes. It takes me forever then to go back and figure out what I did wrong while high; I usually have to wait until I'm sober to debug it. However, the actual logic of the code usually makes sense and it works, it's just little things that I forget or simple errors in logic.
The other problem is that while I can code more mundane code, anything that actually takes a lot of thought is just impossible. I can't remember all the things I'm trying to do and can't keep everything straight. This is just because weed basically destroys your short term memory.
I recognize that weed may give you the motivation to code or give you insight into how to tackle a problem, but just be aware that you'll have to do a lot of debugging of the code after you come down.
As rms said, kratom is a different story. I can code for hours on kratom and actually make very few mistakes.
The other problem is that while I can code more mundane code, anything that actually takes a lot of thought is just impossible. I can't remember all the things I'm trying to do and can't keep everything straight. This is just because weed basically destroys your short term memory.
I recognize that weed may give you the motivation to code or give you insight into how to tackle a problem, but just be aware that you'll have to do a lot of debugging of the code after you come down.
As rms said, kratom is a different story. I can code for hours on kratom and actually make very few mistakes.