Welcome to Duck! The name “Duck” is come from the word “Rubber Duck Debugging”. The https://rubberduckdebugging.com/ website describes the method as below:
- Beg, borrow, steal, buy, fabricate or otherwise obtain a rubber duck (bathtub variety).
- Place rubber duck on desk and inform it you are just going to go over some code with it, if that’s all right.
- Explain to the duck what your code is supposed to do, and then go into detail and explain your code line by line.
- At some point you will tell the duck what you are doing next and then realise that that is not in fact what you are actually doing. The duck will sit there serenely, happy in the knowledge that it has helped you on your way.
The Duck app doesn’t provide the rubber duck itself, and not only for debugging, but the concept to explain your thoughts to something is useful as a thinking process, and it’s also useful if the thinking process can be recorded and referred to later. With the app, you can start thinking by writing a message like “About xxx”, and creating threads for thinking and recording.
Also, the user interface of the chat application makes it easy to write casually. Different from usual markdown note-taking apps, the chat app doesn’t require “create a new note” and adding the title to the note, you can just start typing into a message input form. With the chat user interface, you can record everything in real time, what you did, what you thought, and what you realized. Not only recording the results of your actions but recording your actions themselves is useful as your knowledge base.
I, the author of the Duck app, started development for these reasons. It’s originally from my demand, but if the app can also help you, that would be a great pleasure.