My computer is 11 years old, and even back then it was a cheap machine, so… it works… I can’t say how quickly because I have nothing to compare it with (never ran Claude Code on a different computer) and I can watch a movie while Claude Code is working, depending on the movie resolution. I’d guess it consumes about 50% of the computer’s capacity, so it is possible to do some simple tasks in parallel. It is faster than using a virtual machine. I am okay using it like “I spend 20 minutes talking to Claude Code about what to do in the next iteration, then I say do it, and I do something else, like watch a movie or do the dishes”.
There is one part of your question I forgot to answer, and that is specifically about Python. (I usually work in Java, so I tell Claude Code to make me a ZIP file that I can unzip and run on Windows. Then I copy the ZIP file and it works.) I am not that experienced in Python, but it seems to me like a good idea to use “venv”, which is a virtual Python environment, in other words a system of libraries installed specifically for the purpose of your app. The thing is that pure Python does not have a good way to handle library versions: if you tell it to install library X, it will install the latest version of it. If you need an older version, because the new one is not backwards compatible, you are screwed. You are even more screwed if you have two Python programs who each require a different version of the same library.
The solution to this problem is the “venv” which basically installs the libraries for your program in a separate place, as opposed to directly in the Python installation. Advantage: solves the “what if the latest version is not the best” problem. Disadvantage: slightly more space on disk (installing the libraries separately for each project, even if not necessary), and you need to explicitly start the environment before starting the program.
What I would suggest: Tell Claude Code to create you a ZIP fie containing the generate Python program and two Windows BAT files—one to create the virtual environment (unless it already exists) and install there all libraries required by your program (unless they are already installed); the idea is that this BAT can be used repeatedly if the list of libraries later changes. The second BAT file to activate the virtual environment and start the Python program. And then, the usage is just: double-click “init.bat”, wait until done, then double-click “run.bat” and use the Python program.
You can probably ignore this, because for the freshly written code the latest version will almost certainly be the right one. This is something you may worry about in long term, or if you try to publish the code (when publishing Python programs one should specify the versions of the libraries… somehow).
My computer is 11 years old, and even back then it was a cheap machine, so… it works… I can’t say how quickly because I have nothing to compare it with (never ran Claude Code on a different computer) and I can watch a movie while Claude Code is working, depending on the movie resolution. I’d guess it consumes about 50% of the computer’s capacity, so it is possible to do some simple tasks in parallel. It is faster than using a virtual machine. I am okay using it like “I spend 20 minutes talking to Claude Code about what to do in the next iteration, then I say do it, and I do something else, like watch a movie or do the dishes”.
There is one part of your question I forgot to answer, and that is specifically about Python. (I usually work in Java, so I tell Claude Code to make me a ZIP file that I can unzip and run on Windows. Then I copy the ZIP file and it works.) I am not that experienced in Python, but it seems to me like a good idea to use “venv”, which is a virtual Python environment, in other words a system of libraries installed specifically for the purpose of your app. The thing is that pure Python does not have a good way to handle library versions: if you tell it to install library X, it will install the latest version of it. If you need an older version, because the new one is not backwards compatible, you are screwed. You are even more screwed if you have two Python programs who each require a different version of the same library.
The solution to this problem is the “venv” which basically installs the libraries for your program in a separate place, as opposed to directly in the Python installation. Advantage: solves the “what if the latest version is not the best” problem. Disadvantage: slightly more space on disk (installing the libraries separately for each project, even if not necessary), and you need to explicitly start the environment before starting the program.
What I would suggest: Tell Claude Code to create you a ZIP fie containing the generate Python program and two Windows BAT files—one to create the virtual environment (unless it already exists) and install there all libraries required by your program (unless they are already installed); the idea is that this BAT can be used repeatedly if the list of libraries later changes. The second BAT file to activate the virtual environment and start the Python program. And then, the usage is just: double-click “init.bat”, wait until done, then double-click “run.bat” and use the Python program.
You can probably ignore this, because for the freshly written code the latest version will almost certainly be the right one. This is something you may worry about in long term, or if you try to publish the code (when publishing Python programs one should specify the versions of the libraries… somehow).