dorait
Joined 19 years ago
Joined 19 years ago
Also use Amazon Kindle, Google Play books if I can't find the book on Safari.
Start with a list of ideas - These ideas should be solutions of problems either you face or you see others face - Find 10 people you can talk to about your solution and make a list of features - Pick the core ones and build a functional prototype that people can use and give feedback
Start with a problem (space) - Look for problems that people complain about or ask questions (an analysis of Ask HN is a good source to start with)
Here is one story I read today (I think I found it on HN!)
https://www.linen.dev/s/linen-community/t/545988/from-idea-t...
Wish you all the best. You already took a good first step by asking a question here.
The longer term solution to this problem may be technical consulting.
https://developers.google.com/blockly
High level concepts
1. A workspace 2. A set of pre-defined componets that map to functions or statements 3. A way to connect components to back-ends (like spreadsheets or database columns) 4. Some semantics(behavior) for connections. 5. An implied or explicit sequence of interactions between components.
Can you decouple it from VSCode so that we can use it with other editors like Vi or Emacs?
I struggle with PKM. Stuff is distributed on Google Drive, Github wiki and a few tools like Obsidian.
What do we get by joining the mailing list?
What if the next incremental improvement is asking you questions about the search to get better context before actually doing the search and giving you a smaller set of usable results?
Just dreaming :)
This will start a whole series of next level tasks and some of them you may not even be aware of with just an idea.
Track usage and interest in your prototype and decide whether it is worth building the full product.
Find one similar in your region. If it does not exist, start one.
Coming up with an idea for a product that is useful and that people will pay for is more difficult than actually implementing one.