wastes its time doing these repetitive and boring tasks
To me, this is sort of a code smell. I’m not going to say that every single bit of work that I have done is unique and engaging, but I think that if a lot of code being written is boring and repetitive, it’s probably not engineered correctly.
It’s easy for me to be flippant and say this and you’d be totally right to point that out. I just felt like getting it out of my head.
If most of the code you write is meaningful code that’s novel and interesting then you are incredibly privileged. Majority of code I’ve seen in the industry is mostly boring and a lot of it just boilerplate.
I’d argue that most of the code is conceptually boilerplate, even when you have a framework to paper over it. There’s really nothing exciting about declaring an HTTP endpoint that’s going to slurp some JSON, massage it a bit, and shove it n your db. It’s a boring repetitive task, and I’m happy to let a tool do it for me.
What I’m trying to say is that for Django, especially Django Rest Framework, you don’t even declare endpoints.
DRF has a ModelViewSet where you just create a class, inherit from MVS and set the model to point to your Django ORM model and that’s it. ModelViewSet already has all the implementation code for handling POST, PUT, PATCH and DELETE.
There is no boilerplate.
There isn’t anything that an LLM would add to this process.
Around which parts of Django? Because Django has generic class based views that do exactly the same thing, where all you do is set the model attribute. Then the generic view class you inherited from has the implementation. Especially if you use a ModelForm
To me, this is sort of a code smell. I’m not going to say that every single bit of work that I have done is unique and engaging, but I think that if a lot of code being written is boring and repetitive, it’s probably not engineered correctly.
It’s easy for me to be flippant and say this and you’d be totally right to point that out. I just felt like getting it out of my head.
If most of the code you write is meaningful code that’s novel and interesting then you are incredibly privileged. Majority of code I’ve seen in the industry is mostly boring and a lot of it just boilerplate.
This is possible but I doubt it. It’s your usual CRUD web application with some business logic and some async workers.
So then you do write a bunch of boilerplate such as HTTP endpoints, database queries, and so on.
Not really. It’s Django and Django Rest Framework so there really isn’t a lot of boilerplate. That’s all hidden behind the framework
I’d argue that most of the code is conceptually boilerplate, even when you have a framework to paper over it. There’s really nothing exciting about declaring an HTTP endpoint that’s going to slurp some JSON, massage it a bit, and shove it n your db. It’s a boring repetitive task, and I’m happy to let a tool do it for me.
What I’m trying to say is that for Django, especially Django Rest Framework, you don’t even declare endpoints.
DRF has a
ModelViewSetwhere you just create a class, inherit from MVS and set themodelto point to your Django ORM model and that’s it.ModelViewSetalready has all the implementation code for handlingPOST,PUT,PATCHandDELETE.There is no boilerplate.
There isn’t anything that an LLM would add to this process.
I’ve used Django before and I disagree. 🤷
Around which parts of Django? Because Django has generic class based views that do exactly the same thing, where all you do is set the model attribute. Then the generic view class you inherited from has the implementation. Especially if you use a
ModelForm