Here are some strategies for what I call “creative learning” essentially the idea is that creating something of value comes before anything else, any and all learning shall be done across the journey.
- The cost out-weighs the reward: the reward of a “flashy new idea” wears down as harder challenges come up. It’s the classic conundrum of the “hype” dying down
- Unable to come up with an inspirational idea: not all ideas are born the same, some are either wayy to complex or simply uninteresting (especially if the idea has already been implemented)
- Idea becomes stale: in the project life-cycle without any reason you can simply loose interest, you may find yourself as a zombie, doing the lowest amount of effort possible
All of this poetically relates to exercise and workout, You initially are really hyped and motivated but you have to push yourself just enough to break down the fibres, but not to the point of demotivation
Most of these can be fixed simply by extensive planning. Creating a project workflow/requirement can help a lot, as an example incluide things ranging from the initial UI, to the database tables and interfaces.
- This may sound counter-intuitive, but being a perfectionst about your project can help you relate with it on a deeper level. Most disatisfaction comes with an aspect of project (usually the UI or the user side of it) lacking according to your standards. Aim for a simple interface which you can perfect.
- Look at an existing app with X functionality, make the project, including it’s premium features FOSS. This is a simple yet effective tactic on creating a good product
- Find a niche (that you might belong to) and build out something for that niche, make sure the idea is simple enough that your interest can cut through the challenges
- If you come across an idea you think is revolutionary, keep breaking it down until it is a cog in the system, and then build and perfect that cog for the greater ventures.