AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
The Problem With Requirements of Documentation
You have some static documentation, like some form you send out to everybody. That's how you get enough information to go build the report. But as you start building that report, you realize you're missing a major factor in this. And i think the danger of just relying too heavily, too heavily, because i do believe in eliciting some form of written feedback or, like, implementation wast case strategy,. Is that the devil's in the details, right? It's not the end point.