recentpopularlog in


« earlier   
Guidelines for Human-AI Interaction by Saleema Amershi, Dan Weld*†, Mihaela Vorvoreanu, Adam Fourney, Besmira Nushi, Penny Collisson, Jina Suh, Shamsi Iqbal, Paul N. Bennett, Kori Inkpen, Jaime Teevan, Ruth Kikin-Gil, and Eric Horvitz (PDF, Microsoft)
Группа исследователей Microsoft собрала гайдлайны по дизайну продуктов, использующих технологии искусственного интеллекта. Получилось 18 эвристик, которые достаточно удобно использовать в работе.
UX  AI  algorithms  trends  PDF  whitepapers  patterns  guidelines 
2 days ago by jvetrau
Ant Design - The world's second most popular React UI framework
A design system with values of Nature and Determinacy for better user experience of enterprise applications
components  design-system  guidelines  ux-design  chinese  framework 
7 days ago by gwippich
Fitness function-driven development | ThoughtWorks
Fitness functions strangely put into the context of the test-driven development movement. Targeting non-functional requirements in addition to code quality and test coverage. Examples given include scalability, reliability and observability.

• "Fitness functions describe how close an architecture is to achieving an architectural aim. "

Rough process laid out: [interviews, analysis/grouping, conflict identification, resolution through reframing goals and aligning stakeholders with overall organizational priority]

Now the article moves into some hand waviness around "drafting those functions in a testing framework". The simplest example is something like code coverage thresholds, but elevating from presence to usefulness isn't addressed. It's straightforward to evaluate the presence of logging for example, but harder to evaluate that we're logging the right things. They do pull together a handful of additional checks that could be automated and might deliver some value.

Overall, it's an honest attempt to communicate some of the engineering qualities of a system. Certainly nothing here would survive an attempt to subvert the fitness function, most are trivially exploitable.
architecture  development  work  functionality  guidelines  standards 
13 days ago by devin

Copy this bookmark:

to read