The way this question is framed suggests you might be hitting the same wall most people hit with find.
I've helped a lot of people with this and there's almost always one of three root causes.
**Most likely culprit:** a misunderstanding of the core requirement. This accounts for roughly 64% of cases I have seen.
**Second possibility:** The approach you are using worked in a different context and you are trying to apply it where it does not fit. cheap has specific conditions where it works well and conditions where it falls apart.
**Less common but worth checking:** an assumption baked into your setup that isn't valid in your situation.
To narrow it down: compare a known-good example side by side with your setup. That will tell you which of these you are dealing with.
by justinharris5723
Honest take, because I wish someone had told me this earlier.
Everything you will read about find will make it sound more complicated than it is. Here is what 9 years of working with cheap has actually taught me.
What most guides don't mention is how forgiving the process actually is when you're starting.
What actually moved the needle for me: I stopped trying to understand everything before starting, and just committed to treating every mistake as data rather than failure. After that, things started moving much faster.
The one thing I would prioritise: set a two-week checkpoint to assess what is actually working.
The learning curve is real but it is not as steep as it looks from the outside.
by birukkassa21425