Do indie devs skip code review because it is not fun?

I'm a solopreneur and still review my code before a release / merge into master (I did one earlier today, actually). I've been doing this for a few years and found that it has helped me catch some issues before shipping them to customers. However, I write a lot of code, so my reviews aren't that thorough. They're mostly just to make sure I didn't commit files or changes I hadn't intended to. FWIW I don't enjoy the reviews but consider them a necessary evil.

I think there need to be more info here. I'm a one man shop. I don't have other people to review my code (although it is available on GitHub).

I would imagine that very mall projects have don't have well defined standards or have limited time (volunteers).

Maybe these are weak reason, but I don't know.

I used to work on a team of two and we skipped code review. It was no reason really, just that we didn't see the benefits outweighing the overhead. That was probably wrong, as a lot of bugs, conflicts, and even some documentation could have been avoided if we had code reviews.

There was an earlier situation where we also skipped code review because the coders were all hotheaded cowboys who worked 5 PM to 5 AM, and this was the kind of thing that would just add tension. Also not necessarily a good idea, but we had a high enough political cost trying to implement a daily stand up.