Your goal when you start should be to work on the concepts and to stay motivated. You need to go in-depth when you first start; jumping languages slows that process down.
I would try splitting your program into two six-month blocks instead. The first six months you spend mining university CS courses for some kind of curriculum and assignments; most will be in Java but JS, Python, Ruby or Racket are all acceptable replacements. Try coming up with "fun projects," even if you can't quite do them yet. Other people can tell you what you'd need to learn.
The second six months you spend specifically on your application domain. If it's a web site, you'd learn about database layout, running login and authentication, building a UI, and building the payment mechanisms. All the while you're building prototype code for the final app.
The reason to spend such a large period on the app is because tons of things only come up as you build the app, and they don't appear in general CS, so you can't plan for them, and no book, lecture, or forum post can tell how they're resolved; you have to hack your way through poorly the first time, and then return with better solutions later as the problem fully reveals itself.
You'd also work on getting the other business aspects rolling in the second six months.
I would try splitting your program into two six-month blocks instead. The first six months you spend mining university CS courses for some kind of curriculum and assignments; most will be in Java but JS, Python, Ruby or Racket are all acceptable replacements. Try coming up with "fun projects," even if you can't quite do them yet. Other people can tell you what you'd need to learn.
The second six months you spend specifically on your application domain. If it's a web site, you'd learn about database layout, running login and authentication, building a UI, and building the payment mechanisms. All the while you're building prototype code for the final app.
The reason to spend such a large period on the app is because tons of things only come up as you build the app, and they don't appear in general CS, so you can't plan for them, and no book, lecture, or forum post can tell how they're resolved; you have to hack your way through poorly the first time, and then return with better solutions later as the problem fully reveals itself.
You'd also work on getting the other business aspects rolling in the second six months.