I like to game, but I find the starting of games to be a roadblock. New controls, new features, new concepts, new directives – especially if it’s a “LIKE” game that you have already played before where you already knew what to do in it. The first few weeks of a New Game are critical because you have to commit to the learning, to figuring things out, to walking through what does and doesn’t work…
If you can’t get them to trust each other if you can’t get them to find that common ground. How can you expect them to build an app? How can you expect them to build a system? How can they execute on your system? What will they do when things go wrong? Find the common ground, wherever it is, and start there.
We rush to get to summer, to get all the things off our plate so we can enjoy it. And then we rush to finish summer to get all our things to start what can be considered a new year. Either way, we’re rushing.
Start with what needs to be done. But you know that, and no one wants to start there because that is boring. What you are trying to answer is – “How can I avoid what needs to be done and get to what I want to be doing?” – that’s another question that requires you to go back to the first question – to focus on what needs to get done so you can focus…
I spent the last few weeks trying to create a straightforward no-code app – login page, show a profile – I ended up going back to code to get it done in a few days. If I didn’t know the code, I would have had two options in front of me; Invest myself in a company’s specific framework and learn “their way” to do No Code. Not do what I want, but use some of…