Category

Drive

Category

I have spent most of this week refactoring code. Tweaking it. Optimizing it. Tracking it. Making it more performant, trying to figure out what does and doesn’t work and work, debugging through a mountain of bugs, and generally… making it work. It’s not simple work, it’s frustrating, it’s time-consuming, but it’s always eye-opening how the beauty of simplifying your work, has the potential to work that much better.

I don’t mind the no code movement. But code will never go away. That’s not some kind of die-hard statement on the future of no-code – it will succeed and bring its platform to the masses. But someone is going to have to write all that code. And that’s going to be a lot of fun.

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?

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.