Accelerate you and your team to confidently delivering valuable software and building software teams.
Surprise! Just kidding. There are no surprises in the interviews I’ve done. I tell candidates exactly what’s coming. Why? Because I’m not testing their ability to handle surprises. I’m measuring their ability to prepare and transfer knowledge. The format:
Knowing the format ahead of time doesn’t make it easier. It makes it harder.
Now they have to choose: What passion? What to teach? And then actually prepare.
A friend of mine, Dennis @ Lifeway, is launching a new SaaS plugin product this year. He’s been working on it since last year. I’ll save the details for the end, but I’ve been asking him about the progress and the launch date.
Today, I pressed if there was anything he could do to launch sooner or if he could start talking with potential customers.
Being the cool guy he is, he said I could share. Here is a bit of the conversation and some of the questions I asked him.
I find myself and other teams avoiding writing tests. Mostly because we’re out of practice or if there aren’t enough examples in the codebase.
So, I’ve been thinking about how to make it easier to add tests to your app.
Here, I’d like to share some quick ways to add a test with your next feature, such as bug fixing or refactoring. Here’s the list.
Any new or untested utility function is a great place start writing tests. These functions are typically small and simple to test.