I tried to go into it in more detail here: http://www.berthels.co.uk/2013/03/29/how-do-you-know-what-yo...
Duckie: Rubber Ducking as a service
21–26 of 26 posts
Re: Duckie: Rubber Ducking as a service
#22Earlier quoted context omitted.
There's not that much humor on HN so thank you for making me laugh out loud. On a serious note, to actually infer the type of object, would we need Natural Language Processing or something deeper like an actual AI. Would machine learning suffice (clearly would take a lot of memory). Whats the best approach to the simple task of inferring the object type granular enough to appropriate the situation?
One of the constraints we gave ourselves was that we wanted a fully in-browser solution, and transparently secure - no server-side backend, therefore no data protection issues. With that in mind, any training we did would have to be done by us. This limits our rubber ducking to exploits within our areas of expertise, but does mean that any memory / cpu consumption occurs on the client machine. It is potentially limit…
Re: Duckie: Rubber Ducking as a service
#23It provided me with a really good solution to my problems: Can you describe the problem in a paragraph? Please use small sentences, I'm only a duck. > My colleagues are dumb! >> Is your colleagues the thing that has the problem? > yes >> Can you explain what your colleagues does? > They do very very dumb things. >> Do you fully understand how it does what it does? Could you split your colleagues into smaller chunks?…
This definitely has applications beyond coding: http://imgur.com/62335fX
Re: Duckie: Rubber Ducking as a service
#24Re: Duckie: Rubber Ducking as a service
#25Re: Duckie: Rubber Ducking as a service
#26More info here: https://en.wikipedia.org/wiki/Rubber_duck_debugging
Do you think it would be rude of us to add duckie.me to the list of external links? :)