3 ms·

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 result

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.

Tade0 9y ago
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 overly complicated because somebody lacked the foresight to design the architecture better.
- collyw 9y ago
  What I meant is that with a decent database design, you shouldn't need to much code to get things done (using Django as I am used to). Instead I am jumping from file to file, trying to work out what is going on, what all the seemingly unnecessary code is doing. It can be both tedious and difficult just to get data between the database and a webpage. I want to rewrite a lot of it, but I understand that working, tested code is actually worth quite a lot, and there may be functionality that i haven't understood yet.
- AnimalMuppet 9y ago
  > I think the parent wanted to say that their problems are rather tedious than hard. That idea - the distinction between tedious and hard - is going into my mental toolkit. Thank you.
collyw 9y ago
I never understand why it is looked down upon so much here on HN. Sure anyone can write a crappy insecure PHP for checking a few hundred records. But building a secure maintainable performant application takes some knowledge.

3 ms·

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 result

by Raidion 9y ago

Tade0 9y ago
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 overly complicated because somebody lacked the foresight to design the architecture better.
- collyw 9y ago
  What I meant is that with a decent database design, you shouldn't need to much code to get things done (using Django as I am used to). Instead I am jumping from file to file, trying to work out what is going on, what all the seemingly unnecessary code is doing. It can be both tedious and difficult just to get data between the database and a webpage. I want to rewrite a lot of it, but I understand that working, tested code is actually worth quite a lot, and there may be functionality that i haven't understood yet.
- AnimalMuppet 9y ago
  > I think the parent wanted to say that their problems are rather tedious than hard. That idea - the distinction between tedious and hard - is going into my mental toolkit. Thank you.
collyw 9y ago
I never understand why it is looked down upon so much here on HN. Sure anyone can write a crappy insecure PHP for checking a few hundred records. But building a secure maintainable performant application takes some knowledge.