When to use your mouse, when to use your keyboard, how to locate a file you want to look at in your terminal or IDE, how to find commands you executed last week, etc. It's all lacking. When devs struggle with these fundamentals, I suspect the desire to bypass all this with a singular "just ask the LLM" interface increases.

So when orgs focus on a "devs should use LLMs more to accelerate", I really wish the focus was more "find ways to accelerate", which could more reliably mean "get more proficient with your tools".

I think there's a lot of good that can be gained from formalizing conventions with templating engines (another tool worth learning), rather than relying on stochastic template generation.

    - Slack user detected with full access that isn't associated with a staff-grouped LDAP account
    - Group A in System X doesn't match the members of Group A in System Y)
    - Service Z provisioned, but their associated customer account is deactivated

I suspect it has to do with "camera movement I didn't control". I recall some research done by Valve during the VR development days that resulted in the "teleport" movement fix.

As part of the process, the parliamentary committee released a survey asking questions like

  * Independent candidates should be able to be elected to Parliament
  * The current electoral system adequately reflects voters' intentions
  * Seats should be allocated in proportion to the percentage of votes received by each political party
  * Voters should elect local candidates to represent them in Parliament
  * The current electoral system should be changed

  * There should be parties in Parliament that represent the views of all Canadians, even if some are radical or extreme.
  * Governments should have to negotiate their policy decisions with other parties in Parliament, even if it is less clear who is accountable for the resulting policy.
  * It is better for several parties to have to govern together than for one party to make all the decisions in government, even if it takes longer for government to get things done.

While the following examples aren't exactly _open_ systems, some organizations address the niche you highlight. Examples: https://www.givewell.org/, https://animalcharityevaluators.org/

The same principle could be applied to upvotes/downvotes too, yeah?

- Sum of votes divided by total votes

- More advanced statistical algorithms that take into account confidence (as this article suggests)

- Recommendation engines that provides a rating based on your taste profile

But I'm pretty sure you could take this further depending on what data you're looking to feed in and what the end-users' expectations of the system are.