Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.misc > #17780 > unrolled thread
| Started by | Sylvia Else <sylvia@email.invalid> |
|---|---|
| First post | 2019-04-07 09:25 +1000 |
| Last post | 2019-04-15 20:36 +0200 |
| Articles | 4 — 4 participants |
Back to article view | Back to comp.misc
New development library Sylvia Else <sylvia@email.invalid> - 2019-04-07 09:25 +1000
Re: New development library Batchman <batchman@dosville.foo> - 2019-04-07 21:08 +0000
Re: New development library RS Wood <rsw@therandymon.com> - 2019-04-13 18:34 +0000
Re: New development library Filip454 <filip454.newsgroups@gmail.com> - 2019-04-15 20:36 +0200
| From | Sylvia Else <sylvia@email.invalid> |
|---|---|
| Date | 2019-04-07 09:25 +1000 |
| Subject | New development library |
| Message-ID | <ggsqquF75o1U1@mid.individual.net> |
One of the biggest bug-bears for any developer is that users come to anticipate a particular behaviour from a program. This means that when the developer wants to change the behaviour in a future version, they need to deal with multiple complaints from users who got used to the previous functionality. To deal with this, I have developed a new library, confuseauser.jar. This library allows the developer to specify, for any particular operation that the user may perform, a set of possible responses, and the library will choose one of them at random. This ensures that the user never learns how the application will behave, and consequently that they will not object when it changes. I am fully aware that this technology has already been incorporated into multiple aps, but as far as I can tell, no one has patented it, so I thought that it made sense to provide a simple interface to the developer so that this particular wheel doesn't have to be constantly reinvented. Just a warning, I won't guarantee that future versions of this library will do the same thing. Sylvia.
[toc] | [next] | [standalone]
| From | Batchman <batchman@dosville.foo> |
|---|---|
| Date | 2019-04-07 21:08 +0000 |
| Message-ID | <q8dos0$ptv$1@news.mixmin.net> |
| In reply to | #17780 |
On Sun, 07 Apr 2019 09:25:15 +1000, Sylvia Else wrote: > To deal with this, I have developed a new library, confuseauser.jar. > This library allows the developer to specify, for any particular > operation that the user may perform, a set of possible responses, and > the library will choose one of them at random. This ensures that the Congratulations, wish I had thought of it! Now you'd better start interviewing lawyers, I think you'll need many.
[toc] | [prev] | [next] | [standalone]
| From | RS Wood <rsw@therandymon.com> |
|---|---|
| Date | 2019-04-13 18:34 +0000 |
| Message-ID | <q8ta3p$4n3$2@solani.org> |
| In reply to | #17780 |
On 2019-04-06, Sylvia Else <sylvia@email.invalid> wrote: > To deal with this, I have developed a new library, confuseauser.jar. > This library allows the developer to specify, for any particular > operation that the user may perform, a set of possible responses, and > the library will choose one of them at random. This ensures that the > user never learns how the application will behave, and consequently > that they will not object when it changes. I fully support this! The new generation of mobile devices though kind of already does this. Software you like suddenly insists on updating - or does it automatically - and things change whether you like it or not.
[toc] | [prev] | [next] | [standalone]
| From | Filip454 <filip454.newsgroups@gmail.com> |
|---|---|
| Date | 2019-04-15 20:36 +0200 |
| Message-ID | <q92iv7$n6a$1@news.icm.edu.pl> |
| In reply to | #17809 |
W dniu 2019-04-13 o 20:34, RS Wood pisze: > On 2019-04-06, Sylvia Else <sylvia@email.invalid> wrote: >> To deal with this, I have developed a new library, confuseauser.jar. >> This library allows the developer to specify, for any particular >> operation that the user may perform, a set of possible responses, and >> the library will choose one of them at random. This ensures that the >> user never learns how the application will behave, and consequently >> that they will not object when it changes. > > I fully support this! > > The new generation of mobile devices though kind of already does this. > Software you like suddenly insists on updating - or does it > automatically - and things change whether you like it or not. > Auto-update is one of the biggest cancers (well, let's say tumors) of our times. -- Filip454 [filip454.newsgroups@gmail.com]
[toc] | [prev] | [standalone]
Back to top | Article view | comp.misc
csiph-web