Technical books using https://learning.oreilly.com/home/. I have been a subscriber for more than 10 years, dicontinued for a few years and resumed about a year ago.
Also use Amazon Kindle, Google Play books if I can't find the book on Safari.
There are lots of good resources as mentioned by others. Here are some starting points.
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!)
Some companies do provide a technical track in which you can become a Principal Engineer with no management responsibility. But if you have experience in solving problems, you may be good as a mentor/coach to other devs.
The longer term solution to this problem may be technical consulting.
Blockly is an example of no-code app that generates code. It is a good starting point to understand how you can build a no code framework. Blockly is...
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.
"find your first 1-10 paying customers yourself". I agree with this. Going through this will show you whether your product is really ready for the market and customers perceive enough value to pay for it. This part cannot be outsourced. This is the founding teams job and is as important as creating a product (sometimes even more important).
Also use Amazon Kindle, Google Play books if I can't find the book on Safari.