No plan, no action. No action, no results. No results, you never had a chance. The plan doesn’t have to be complicated. I still can’t get into any type of project software and find bullet points and checklists the best thing available to me. But there is always a plan.
If your framework is overcomplicated, if it requires many steps to get up and running. If the space between start and success is a long battle fraught with many discussions, forum posts, and chats to get there. Chances are adoption won’t happen as quickly as you want it to. Adoption, in any framework, is key and critical to design. If people can’t easily get into it, it doesn’t matter what it can do.
Getting in the zone is the best thing – you’re focused, and on point, things work, and nothing can fail. The question is whether you can get there when not prompted, or can you get there on your own, can you figure out a path to get to the zone when you are not prompted? Get prompted, getting told to do something to get there to get into the zone is easy, getting there on…
If you never lose, you never know what to work on. When you lose, you know what to work on next.
As often as I forget, I am just as quickly reminded, that all development is on the fly. You can do all the courses, go through all the reading, and understand what is needed where but at the end of it all, you are always doing development on the fly. You are always learning what needs to be done in the moment and figuring out the approach to get there and make it a success…