Recorded – watch the full episode on YouTube.
Where are you with testing now? Have you any tips on how to start?
Sean Allen: I'm looking at it through the window, like it's right there, I'm reaching for it. We're still not fully involved in testing yet, but we're getting closer. Let me just say this thing about learning: learning evolves over time. I think a lot of beginners can try to put too much on their plate right away, some five years in my career and hadn't even really tackled testing.
I'm not saying that's the right thing to do by any means, but I don't think I'm a horrible programmer because I haven't tackled testing. It's absolutely a skill that I need to tackle. I know it's a hole in my game. I recognize that. But I think forgiving yourself and letting yourself learn over time and evolve as a programmer is the way to go in my opinion.
“Read some books, do some tutorials, put it into a practice project. I like to fill the holes anywhere that I feel like I'm weak. And I feel like now's the time to fill that hole, just do nothing but that for the next X amount of time.”
So if you're uncomfortable, you're getting a lack of confidence, running clean testable code, just work on it. Again like I had mentioned in the closure example, if that's your pain point, you're self conscious about that. Like that weighs on your confidence. Focus on that for the next two weeks, read some books, do some tutorials, put it into a practice project.
I like to fill the holes anywhere that I feel like I'm weak. And I feel like now's the time to fill that hole, just do nothing but that for the next X amount of time.
This transcript was recorded as part of Swiftly Speaking. You can watch the full original episode on YouTube, or subscribe to the audio version on Apple Podcasts.
SPONSORED Check out Stream's cross-platform open source chat SDK on GitHub! Write once and deploy your app with fully featured chat UI on iOS and macOS.
Link copied to your pasteboard.