Think about how hard it would be to get all of humanity to agree on and learn one language. It’s impossible right? Even if we made contact with aliens who told us they would destroy the planet unless we all learned one language it’s still not going to happen. Coordination at that scale is out of humanities grasp right now and even getting a group of people to agree on anything is rough.

The other day I noticed I don’t follow any tech bloggers personally anymore. Some of that may be the rise of social media and aggregator sites filling the void but the bigger reason I think is that I haven’t been seeking out individuals to follow since around the time Coding Horror stopped blogging regularly. It’s a bit of a shame really since I think you can learn a lot by following individuals and seeing their own progression arc.

I’m finally getting around to putting down in words the testing philosophy I’ve developed over the years. Some of it might rock the boat a bit, other parts may be obvious to some folks, but what I’d like you most to take away is a reflection on your own testing philosophy and the tradeoffs your making. There’s no free lunch.

If you’re running a Next.js app and want to test it with Cypress you probably noticed a problem when it came time to test a server side rendered page. There’s no built in way to mock out requests made in getServerSideProps. When I ran into this and searched around for solutions I found this article that has a good explination of the problem (and diagrams), but I wasn’t satisfied with any of the solutions.

Have you ever had that brainfart moment when you’re writing code and forget what syntax you’re supposed to be using? An example is helpful: