3 ms·
And on the product side you have product requirement docs which was always useful when a new feature came up as it aggregated all contacts, documentation, suppo
by dudus 2y ago
And on the product side you have product requirement docs which was always useful when a new feature came up as it aggregated all contacts, documentation, support, communications, etc. You always want to work in a product that maintains a decent one.
- smokel 2y ago> You always want to work in a product that maintains a decent one. That'd be lovely indeed. I have never seen one that I felt comfortable with, though. And I've seen a few. When LLMs rose in popularity, I had hopes of having a way to tackle the problem of formulating requirements in a way that would be less painful than it is now. To me, computer programming is a form of communication, where the requirements are close to humans, and program code is nearer to the machine. On the computer side, we have linters, compilers, and a deterministic system that executes the code. On the human side we have people stating requirements such as "The system should be easy to use."