I'd like to write more, but I want to make sure my writing adds value. In my opinion, boring, rehashed content floods the internet, and I hope that I don't contribute. I've set a goal to write a new blog post every month with the caveat that the post needs to be valuable. Hopefully I will accomplish that.
My new post tries to talk about issues around technical interviews in a different way. I've read a lot of articles over the years about how technical interviews are broken. Most of these articles complain about doing algorithmic coding questions for a job that involves very few algorithmic use cases. I agree that using algorithmic problems to interview web developers sucks. Instead of talking about why that sucks, I discuss my favorite technical interview, and why I think it's awesome.
Thanks for reading,