|
|
|
|
|
by izzie1234
108 days ago
|
|
I love this idea. I see the AI era having 2 competing views when building something new: 1. Build X with pure <language of choice>. Why? LLMs will have less context needed, and onboarding engineers would be easier since there’ll be less overhead and opinionated frameworks knowledge required 2. Build X using well establish frameworks. Painful in the beginning since you’ll not only need language knowledge, but framework knowledge. The upshot, is scaling and maintainability I love that this ecosystem will heavily pressure teams to consider (2) more and more — solving the very real “AI slop” problem |
|
In my view. Building things with AI creates the need for common patterns and guardrails (i.e. frameworks) Then as these new apps become productionalized - tooling that fits your framework starts to become more important.
In that sense, AI increases the need for good patterns around observability. This project aims to make this a little easier to do for Django right from inside the framework as opposed to an external service.