4 ms·
No, see that's the problem. Way too many resources. I LOVE the idea of one book that takes me from start to finish, with no flab or wasted time learning somethi
by contextual 13y ago
No, see that's the problem. Way too many resources. I LOVE the idea of one book that takes me from start to finish, with no flab or wasted time learning something that isn't 100% relevant to making an app.
Alex, you are on to something HUGE. Resist with all your might the urge to bury people in "resources" to follow up on. There's too much information out there. Reign it in, filter it down and focus only on the bare minimum that must be done to get the app finished.
Not everyone wants to be a programming guru. Myself included.
- angersock 13y agoMaybe you shouldn't be building an app, or programming, especially if you don't care enough or have the patience to learn things that aren't directly in support of (what you think is) your MVP.
- contextual 13y agoWho said anything about patience or not caring? I didn't.
- angersock 13y ago* I LOVE the idea of one book that takes me from start to finish, with no flab or wasted time learning something that isn't 100% relevant to making an app.* These do not appears to be the words of a patient person, or somebody who cares about programming. I suggest that the impatient and uncaring should not be making apps.
- deleted 13y ago[deleted]
- alex_c 13y agoI strongly, strongly disagree. You can approach programming as a craft, and immerse yield in tools, techniques, concepts and so on. Or you can approach it as a means to an end, which is creating an app, website, service, etc, and just look for the shortest path to get results. You don't have any basis for saying one approach is more valid than the other.