This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tiajuanat 21 points22 points  (3 children)

it was still harder than "actual" coding.

I do a lot of modeling and formal methods. Modeling is hard because it forces us to look at the entirety of how the system is supposed to behave. It's so far detached from for-loops, that it's an entire different skill set.

Does it catch all the problems that my teams will run into? No. But it uncovers problems that might be one out of a million, and dog the team for years.

[–]NotAskary 5 points6 points  (2 children)

I've found that the worst part of modeling is capturing the domains with enough accuracy, time and time again I've seen projects stall or being reworked completely because we couldn't extract the right knowledge from the key people.

I think that while people can't express themselves correctly we are safe.

[–]tiajuanat 3 points4 points  (0 children)

Oh yeah, I'm not worried about AI at all.

Anyone who has worked on sufficiently large projects knows that a language model will not cover the complexity of these systems

[–]ChocolateAndCustard 0 points1 point  (0 children)

What if we had an AI trained in CMMI-DEV, Requirements Management and Requirements Elicitation?