You miss a deadline. You miss an event. The work you put in didn’t pan out. The code you wrote still doesn’t work. The rules are broken. The game is old. Time to get back, time to build something new, time to refocus and not forget why you got started here in the first place.
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…
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…
And other great developer messages… “Build Succeeded…” “Unit Tests Passed…” “Successfully Deployed…” “Pipeline ran Successfully…” Amazing how much joy these few messages have brought me over the years.