alt Hacker NewsWhat about brownfield development though? What about vague requirements or cases with multiple potential paths or cases where some technical choices might have important business consequences that shareholders might need to know about? Can we please stop pretending that software engineering happens in a vacuum?
Replies
kaibee • last Wednesday at 5:31 PM
> What about vague requirements or cases with multiple potential paths or cases where some technical choices might have important business consequences that shareholders might need to know about?
If the cost of developing the software is 0, you can just build both.
➕ show 1 reply
squidbeak • last Wednesday at 4:21 PM
Isn't what you describe eventually just a context contraint problem?
The thing with vague requirements is that the real problem is that making decisions is hard. There are always tradeoffs and consequences. Rarely is there a truly clear and objective decision. In the end either you or the LLM are guessing what the best option is.