There is never enough time to take a step back and figure out what is wrong. Never. Ever. Until it breaks and then you have a ton of time on your hands to figure it all out, design the perfect solution and fix everything that was wrong. That’s odd, I thought there wasn’t enough time?
At a new job, new project, we all need help to get started and figure out what we’re actually supposed to do. “What is this bug? What am I suppose to do with it? Where is the code? How does it work?” In the back of my head, I’ve always had a hidden evaluation metric running where I want to see how far you can get to after Step 1. Do you go from Step…
I’ve written before about going into a cave. Sometimes you need to do it, sometimes you need to leave your team to do it. But you can’t do it every day. You can’t do it all the time when something goes wrong. The cave is where you are most productive without hindering your team’s productivity. If you’re always in the cave, you’re not doing you’re best work, you’re hiding.
Keep doing it. Over and over again until you get better. Don’t stop, don’t worry about what was goes wrong. Just keep doing it. Improve, learn from your mistakes, find gaps and make them better. But don’t stop. The fastest way to not getter is to stop.
Coding with a team is like a relay race. Everyone runs (Sprints) as fast as they can, they go all out, pushing as hard as they can until they can’t go any further, and then they hand off to their teammate, who goes and does the same thing. Everyone’s top speed is different, but we are all driving towards the same goal. And no one can do it alone.