|
|
|
|
|
|
by ammar2
2500 days ago
|
|
|
Sorry if I'm missing something obvious but it's not very clear to me how the first part significantly benefits from AI. Code re-use is just good software engineer practice, are you somehow able to figure out what libraries to use automatically? Isn't this trivial to perform by a human anyway? The latter part, as far as figuring out what work to assign and estimating time-frames does seem like a legitimate AI use case though. |
|
|
We're attempting to tackle the problem holistically. That means that we're tackling every single step of the traditional product development process. All the way from how you ideate, price, and spec, to sourcing and managing developers through to QA and infrastructure management.
For example, today, our ideation/pricing/spec tools leverage applied ML, creator management leverages facial recognition for fraud prevention, and infrastructure management uses statistical modelling.
We're trying to make code re-use a repeatable and predictable process rather than just a best practice. Today in the industry it's a purely led by developers, and very often is done solely at their discretion in a manual fashion. We're attempting to platform enforce code reuse, across autonomous distributed teams and products. Apart from just deciding what the optimal building blocks for a project are, the actual assembly or intelligent merging of these building blocks in an automated way is non trivial and mirrors modern automative assembly lines.