Earlier quoted context omitted.
I mean, CRUD doesn't have to be simple. It can get complexity from the underlying data, or dealing with 100 million users at once, or it having to return results FAST. Just because you don't have to write some novel algorithm doesn't mean you're not solving hard problems.
I think the parent wanted to say that their problems are rather tedious than hard . I'm currently in a very similar situation - a project in which we have a table of records, two of which are special in a certain, business-related way, but need to be presented along with the others, so to get around this we place "ifs" here and there - a lot of them. It's a generally simple project that has been turned into something…
That idea - the distinction between tedious and hard - is going into my mental toolkit. Thank you.