4 ms·
> So, a lot of engineers that are just doign teh same old trick: Writing HTTP endpoints, parsing json. Mapping data types.. Yes that could be automated. And to
by Yoric 4y ago
> So, a lot of engineers that are just doign teh same old trick: Writing HTTP endpoints, parsing json. Mapping data types.. Yes that could be automated.
And to be fair, automation for all of that already pretty much exists.
- coldtea 4y agoAnd to be fair, even though it exists, there's a huge majority that is done manually, even though it needs zero or very little manual "creativity" between specification and implementation
- gombosg 4y agoI agree. Usually you're already working within some framework or DSL where you can describe what you want to do. Ideally, you already have an idiomatic codebase enabling you to succinctly transform specifications into code. Let's take parent poster's issues: > Writing HTTP endpoints, parsing json. Mapping data types. The generative model (for now) won't figure out for you: authentication, authorization, input form schema, JSON schema, required & optional fields, field constraints, entity modeling, indexing, query optimization, just to name a few basic issues we are looking at when "just developing CRUD apps". If any of those go bad, it would result in 400s, 500s, performance or security issues.
- raydev 4y agoIt is exists where it can be supported. Lots of small businesses don't have the bandwidth to maintain additional infra that automates this sort of work. Which sorta brings me back around: it's likely the Big Corps that are going to be trialing GPT first because they have the excess money and resources to play with it. How useful will it be in the end?