osmarks/website
1
0
Fork 0
mirror of https://github.com/osmarks/website synced 2025-09-03 11:17:55 +00:00
Code Issues Releases Wiki Activity

minor updates, about me page, new post

Browse Source
This commit is contained in:
osmarks
2024-05-12 01:24:58 +01:00
parent ed52fa9c24
commit f92ae04d98
9 changed files with 96 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog/stop-making-chatbots.md
View File

@@ -22,7 +22,7 @@ There's also the issue of predictability: a good interface agrees with the user'
Think about what workflows your users need and how you can serve them with a well-scoped UI rather than pretending to handle every possible input[^5]. Make your interface feel like a predictable, trustworthy tool rather than someone you might delegate work to, unless it actually can have work reasonably delegated to it. A really good tool should do what you mean, anticipating your desires and needs[^4], and AI can help with this, mostly in unflashy but helpful ways - the primary uses being good semantic search and recommender systems. Something like a documentation website should just have good organization and helpful search, maybe with an inline summarizer; forms can just be forms, maybe with AI (or regexes) to point out possibly erroneous inputs; a dashboard should present the most important information upfront and any recent changes or anomalies rather than requiring a dialog tree. In general, subtle uses of AI in areas it's competent are better than trying and failing to emulate a human.
[^1]: My thoughts on fictional magic systems are to be made available here later.
[^1]: My thoughts on fictional magic systems are ~~to be made available here later~~ [now extant](/magic/).
[^2]: I don't really know why this is the case, but it's probably for the best.