I can read code and know some basics in C, Java, and Python, but I struggle to figure out which modules to use and how to turn an idea into smaller tasks.
For example, I want to make a disk cleaner that finds large files and suggests what to remove. I get stuck just trying to make the window. How do I start without already knowing all the pieces?
Skip the window for now. Make a console program that lists the files in one directory. Then add their sizes, filter out anything below a size you choose, and sort the remaining files by size.
Once that works, look into visiting subdirectories. Treat each step as a separate problem you can search for and test. A finished little file listing tool is a useful first version, even if it doesn't clean anything yet.
The recommendation part needs a more concrete rule before you can code it. What does a file being a good candidate for removal actually mean? You could start by showing files above a chosen size and letting the user decide.
Write the steps in plain language first, including what happens if a folder can't be read. Then pick one step and figure out how to express it in your chosen language. You don't need the whole design solved before writing any code.
You aren't supposed to memorize every library. Pick one language for this project, search its documentation for the specific job in front of you, and try a tiny example before adding it to your program.
For instance, first look up how that language lists a directory. Get that working on its own, then look up how to get a file's size. Check how to import or access the relevant library in the documentation rather than trying to guess it all upfront.
Your project doesn't have to be original. Rebuilding a simple existing tool is perfectly good practice, and it saves you from spending all your energy inventing an idea. Pick a small feature set you understand and try to finish that version.
If making a window is the part you want to learn, isolate that too. Make a tiny program with one button, get it working, and work through what each part of the code does. You can come back to the disk tool's interface later instead of learning the GUI and filesystem code at the same time.
Answers are reviewed before publication.
x.483!tagwhistle:
Keep it read only while you're learning. Listing a file as a candidate is very different from automatically deleting it.