hagg3n
Joined 9 years ago
Joined 9 years ago
To me, it just feels like when I scan some text with the eyes looking for the juicier parts or hooks that I most care about. Speaking of which, I much prefer to consume content as text than audio or video. I can scan, seek, pause, think, go back at will without fiddling with any controls.
I have lost jobs and annoyed people trying to argue for greater care with accessibility. It's somewhat depressing.
I never thought I should handle each and every case, just be mindful of the assumptions I'm making.
Sure I can agree these tools are worth learning, I'm just pointing out it's not the same thing. Netlify allows you to setup a static website with data collection, e-mail dispatch and whatnot all without code and much faster.
Should whether an application is running or not be a concern to you? Why would you ever want to actually quit an application?
Granted, I understand that in reality the app might be misbehaving, hogging resources and whatnot and that the underlying OS isn't perfect and we should absolutely have control over how our hardware is utilized, but from a UX PoV I think the notion of a running process isn't of interest to me unless I am developing software.
If I close a window, I just want to get it out of my way. I only leave things running as a workaround to the possible slow cold start the program may present.
Picking a tool and setting up a knowledge base to have technical and design decisions, notes, and maintenance logs in a single place is usually straightforward. It's the consistently feeding the system with high-quality data part that we get stuck at.
Eventually, I have to input information when I lack the necessary mental bandwidth, I end up creating incomplete entries that lack essential details.
The initial idea is to develop a chat interface that allows us to share random pieces of information, either through text or voice, and have it scanned for actionable data that can be ingested. Then it should start probing the user, looking to expand and refine the new information, connecting it with existing data, and general maintenance of the repository. All with no active guidance.
For instance, I could launch it and say: “Today the team and I discussed how frequently the databases for project A and B should be synced. We established the user can tolerate up to 10 minutes of tardiness", at which point I would expect it to:
- Create a note of this discussion happening - Check and fix the existence of entries for projects A and B - Link the note to the projects - Create database entries for both projects - Look for previous entries that could be linked to the projects - Ask for further explanation of how we came to that conclusion