On Arch: Randomly pull it in from the repos or AUR, fiddle with it till I am bored, then figure out if I have a real use for it. 90% of the time it is a no, but I have found some really neat stuff out in the wilds.
In production: Search for software based on a need. Read the docs first. Install in a dev docker and test it. Ship docker to production once I understand it.
When its Linux/Windows productivity or even general utils. I've often read a solid 1/4 to 1/8 of the documentation trying to ensure this tool will fit my use case, isn't malicious, etc.
Once I've downloaded and installed it, I generally just use it.
Generally I only download/install new software because someone I trust (or a news site I trust) told me to. So my use case is already constrained initially to the use case I was introduced to by someone else.
Yes, UI has to be totally intuitive!
If you had discreet event-driven notifications (NOT like that awful paperclip that MS Word had) that give you the right information at the right time, would that be useful?
Assuming you could turn them all off if you wanted.
You mean like the guided tours that 'patio11 made a video about that I watched recently? :P (I recommend the http://www.kalzumeus.com/ mailing list if you haven't seen it yet)
This is very interesting, totally assumed the other way round. But I guess it's easier than pausing, rewinding, doing it in the application etc.
Thank you for this insight.
