I read a plethora of Choose Your Own Adventure Books as a kid – they were great. I don’t know what today’s equivalent of them would be. But as I was writing this article, I could smell the paper, feel the book in my hands and was flooded with memories of flipping back and forth trying to outsmart the author – I never did. But here it is – Choose your Own Adventure.
The only way to go is down when digging a hole. When you hit a rock, you switch from the big awesome tool to the small tiny tool that is slower progress but gets the job done. When one obstacle is cleared, you keep digging further and further until you hit the next one. Until you finally hit the bottom, and then you’re there and you’re done. You never know how far you are to…
The best thing about writing code is the immediate feedback. It works or it doesn’t. Your code pumps out oodles of value or it returns bugs. Bugs are great, they never go out of style and you get the same level of response to what you are doing – immediate feedback as to whether you’re on the right path or the wrong one. Never fear the bug, fear the program that has no bugs.
If there was a definition for being overqualified for an opportunity and still getting the job done, it is this video. Don’t forget to have fun. https://youtu.be/RvatDKpc0SU
Doing everything differently for every project isn’t going to help you move faster. Redefining your methodology during a project is never going to work, that’s an outside-of-project task when no project will be affected. Tweaks are good, but changes are not good. Tweaks – “Let’s log these types of issues as bugs instead of tasks” Changes – “Let’s stop using sub-tasks and stories and go to epics and tasks” Your methodology might not do one…