news.volyx.in

When users never use the features they asked for (web.eecs.utk.edu)

583 points by jermaustin1 · 1819 days ago · 219 comments on HN

Article summary

The article discusses the phenomenon of users asking for features that they ultimately do not use, and the importance of understanding the underlying needs and workflows of users. The article's contents are not directly available, but the discussion reveals that it touches on the challenges of building internal tools and the need for a close relationship with users to validate what's being worked on. The article may also discuss the role of automated analysis and code review in the development process. The main point is that users may not always know what they want or need, and it's up to developers to understand their requirements.

Main themes

  • user needs and workflows
  • automated analysis and code review
  • feature development and prioritization
  • design and usability
  • communication and update processes
  • user behavior and expectations

What commenters say

  • Users often ask for features they don't end up using, highlighting the need for developers to understand the underlying needs and workflows of users.
  • Automated analysis and code review can help streamline the development process, but may not always be effective in catching errors or improving code quality.
  • Some argue that building features that users ask for can be a waste of time and resources, as users may not ultimately use them.
  • Others believe that understanding the problem and presenting possible solutions can lead to more effective and useful features.
  • The design and usability of a feature can make a big difference in whether users adopt it, even if it's something they initially asked for.
  • Developers should be cautious of over-reliance on automated tools and focus on understanding the needs of their users.
  • Users may not always be able to articulate what they want or need, and it's up to developers to ask questions and understand their requirements.
  • The update process and communication with users can also play a role in whether new features are adopted or not.