Fire up your hot takes, folks. This is going to be a fun one.
Whether you're early-career or have been coding for decades, nearly everyone has got a coding exercise story (or stories). And feelings too.
What makes for a good coding exercise? What makes for a bad one? Why is to so hard for companies to assess developers' technical skills? Is live coding better than take-home? Should they be timed? Should companies pay candidates for their time? What's the most equitable way to do coding exercises? (and the list goes on)
There are so many things to talk about here, and we're going to do our best to talk about all of it!
More details to come.
Matt (he/him) is a self-taught software engineer, entrepreneur, and pizza enthusiast. He's been through many transitions in his life. Past projects include Invisible Network, Mpls Jr Devs, and OMG Transit.