4 ms·
I have a colleague like you. Your problem is this: you say you want to build something cool, but then you follow up with "but every tutorial I read..." There i
by readme 7y ago
I have a colleague like you. Your problem is this: you say you want to build something cool, but then you follow up with "but every tutorial I read..."
There is NO guide to building something new and cool. Yeah, you will build upon existing stuff, but you need to come up with your own plan and then research specifics to fill in the blanks. You may have to repeat work, so just accept that.
- not_kurt_godel 7y agoThis is great advice. Stop making "learning the framework(s)" part of the goal. Pick something that is in the rough genre of what you want to do, and bulldoze through it to Do The Cool Thing. Accept that you will be working inefficiently and painfully at times. That's how you gain experience, and through that experience you will grow an understanding of how the frameworks differ from each other and which are most suitable for certain kinds of tasks.
- dwg 7y agoCompletely agree. Your only goal is build then launch. Be 100% focused on this. Reading and learning will be required, but should be set against a specific task that is part of your product launch goal. You only need to research as much as is necessary to achieve the next task (that gets you closer to launch). Then you move on. Your code doesn't need to be a masterpiece. It just needs to work. You don't know which idea will be a winner, yet, so save the really hard work for the idea that sticks.
- bubblesocks 7y agoI agree. "Something cool" is something that doesn't exist yet and it is really hard to find tutorials on those.