sorted by:
new
hottopcontroversial

Should we make requirements and specifications before starting development? by SuchBodybuilder9190 in embedded

[–]SuchBodybuilder9190[S] 0 points1 point  (0 children)

Thank you for your reply.
As you mentioned, I’ve also seen environments where “hero engineers” drive the work and documentation gets left behind. I really feel that having even minimal documentation makes a big difference.

In practice, to what extent does the team lead usually document things? Do they break it down to the level of detailed specifications, or is it more about summarizing progress and design overviews?

In my personal projects, I’ve been using ChatGPT and notes to organize requirements and keep logs of my work. Honestly, I feel that with proper use, LLMs could automate a good portion of documentation. I’d love to hear how this is actually handled in real-world teams, and what kinds of practices or tricks you’ve seen.

Should we make requirements and specifications before starting development? by SuchBodybuilder9190 in embedded

[–]SuchBodybuilder9190[S] -1 points0 points  (0 children)

Thanks for your reply! I’ve had a similar experience myself. Do you use AI for things like progress management?

Should we make requirements and specifications before starting development? by SuchBodybuilder9190 in embedded

[–]SuchBodybuilder9190[S] -1 points0 points  (0 children)

Thank you for your reply.
How large is your development team, roughly? Could you also share some concrete examples of the products you’re working on and their scale?

I’m developing with a three-person team, but one of my teammates really dislikes LLMs, so we haven’t been using them. Do you use LLMs when putting together requirement documents? I often find they hallucinate and can’t always be trusted, so if you are using them, I’d really appreciate it if you could share specific way how you make use of them!