Another iteration went up last night, killed the app overnight, fixed the app (needed to update a config setting that worked locally, but not in the cloud - DOCUMENTED FOR THE FUTURE), aaaand… it’s not really all that visible a change.
I’ll have to think about this some more.
When I dump out 100 phrases locally I immediately spot lots of teh funny. Not so when it’s only once per hour.
However, a lot of the work I’ve been doing has been to make things more modular and add tests – so I can now iterate a bit faster and securely. HOPEFULLY.
As usually, all of this is boring stuff nobody cares about.
Thanks! I went to a botmakers slack (that I’ve been mostly low-level lurking on) to see their reactions, and discovered the author of the NodeJS portion of the BotFramework had just joined up!
I’ll look at it later. I think the thing is mostly for interactive bots - which may be “the future” but it’s not my bot area at the moment.
Today’s output looks a bit better, but there’s still too much repetition. The app is running on Heroku’s free plan which requires 6 hours of downtime a day, so is triggered once an hour by their scheduler. Which mean no saved state - so instead of randomly cycling through a diminishing array (pick and remove) it randomly picks from the full array each time. It’s a small array, and the random generator seems to specifically want to annoy me.
Well, I’d suggest that an obscure 1950’s reference is not the one to use if on top of being wildly out of date it’s also causing you to spell a word incorrectly. It makes you look like you don’t have good information. That’s the opposite effect of what you’re trying for!