https://daily.dev/blog/what-is-devin-the-ai-software-engineer-everyone-is-talking-about
6 replies (most recent on top)
But this assumes users know what they want… I think Software Engineers are safe.
Pretty much.
There are several ways to reengineer WF tech. The way I think WF is doing this is as follows:
- get knowledge of all of the existing applications. Detail what they do. Detail all WF application's CRUDs processes on these "what sources of record". Detail rules for creation.
- Start developing domains of the above. These domains will be serviced based (aka Wellsfargo gateway)
- Create a model of the customer, the 'service customer domain'.
This is done at first by process engineers (BEP), surveys, product development -- later by the system itself (e.g. process "fargo" requests to see if the customer needs something that is not being provided, mistakes, etc)
- Map created domains and domain interaction to create the WF banking model. DDD (domain-driven design) will be generated by AI.
- AI compliance will be done by comparing the above-generated WF banking model against "standard" consultancy banking models.
- Implement. The AI will not only generate the code but also be the basis for the infrastructure. The upkeep of the data, and the "sources of record" is maintained but done with more documented and tested rules.
Where does the "customer" fit into all of this? In the "old" days you had business analysts ("roughly" BECs in WF's vocabulary) whose main job was to elicit the user/customer needs and convert them to software requirements. This construct changes in the AI-driven world. One of the first domains to be modeled will be the "customer". This allows everyone, no matter where, to "know" the WF customer. The engineer can be 8,306 miles away from the closest WF US bank branch and still be able to know the WF customer!
The bank could maintain the existing architecture. (UI -- application --data (SOR)) or go to a new architecture UI-Domain/Service API- rules/process-data (SOR). In a couple of months (after the notices expire) we will get more clarity on which way WF is going.
Yes
Eventually, as we currently know the role, yes.
But.... Once AI is good enough to nearly write an entire program, it's not like companies are going to let today's productivity be good enough in the future.
The number of concurrent software projects will multiply because the evolved role of the SWE will be to read through the AI output and make corrections as needed. That's a lot faster than starting from scratch.
But eventually software will entirely write other software by just being fed plain English requirements. Crazy.
Duh? Ya think?