4 ms·
IF LLM do translate so good English somehow directly in “code”, then there are much more job in the line that just coders, and many tools that could be rendered
by f1shy 1y ago
IF LLM do translate so good English somehow directly in “code”, then there are much more job in the line that just coders, and many tools that could be rendered obsolete. Indeed fact the whole chain, from customer to, well, back to customer, could be replaced. Requirements elicitation, writing requirements, making a design, architecture, even tests (shloud we need them?)
As far as I know and my experience confirms (maybe biased?) the whole chain of SW engineering is there precisely because English is not always optimal.
Indeed fact fact in a project I directed, the whole requirement management was basically a loop
Repeat{talk to customer; write formal language; simulate; validate}until no change;
It was called “runnable specification” not my idea. It worked absolutely incredibly good.
- ttoinou 1y agoWhat's the simulate and validate steps ?
- f1shy 1y agoThe written requirement were written in C, C++, python, Verilog, Systems C. So they could be run. The runs were sent to the customer who would validate (approve) or reject.
- ttoinou 1y agoThat's pretty much how everyone is doing it, no ? It's a (Think a new improved model, Code the model, Study Results and compare with what we thought about the model) cycle. What's the alternative ?
- skydhash 1y agoI think the issue is how people goes about doing it. Often the model is clearly not improved, but it would mask problems some people wants under the rug. Sometimes, people are coding the wrong model or coding wrongly the correct model or coding wrongly the wrong model. Sometimes there's no study being done, only hope and prayers. And comparing is only ever done by the customer.
- f1shy 1y agoMmm bot really. First, it was HW and SW, and HW was simulated. Many go on to build something, then test Second, requirements are written in a formal language. I’ve never seen formal languages in DOORS (or similar) before Third we did not do the whole thing, just the bits and pieces in the requirements. After the requirements were done and approved, we move on to development, where the “normal” iterations happen. Subtle, but not the same
- skydhash 1y ago> Repeat{talk to customer; write formal language; simulate; validate}until no change; That's basically the agile manifesto, but involving flexibility by having humans instead of policies defining the flow and shorter iterations.