I'm a much bigger fan of telling someone they have 24h to build me a toy deliverable to test how well they can work under pressure and scrape code together. That gives you a better understanding of how well they can do that on the spot just make sure to have then walk through the code the next day so you know they actually wrote it
Whiteboard exercises are a terrible way to investigate coding ability (2012)
41–42 of 42 posts
Re: Whiteboard exercises are a terrible way to investigate coding ability (2012)
#42I'm an anomaly. I like whiteboard algorithm tests. I do still think it is kinda a waste of time doing Leetcode over and over like what I'm doing right now, but hear me out. An even more waste of time is actually learning framework A, B, C, D, database A, B, C, D, bundler A, B, C, D. The more and more I think about it, as a fullstack developer, I continuously forget documentations and how a specific technology works,…
I had this problem with switching contexts. For work, we use a combination of old Java, Tomcat, JS and the likes. For my hobby, I mainly program games in C#. Two entirely different infrastructures. That said, I can keep both up decently well due to the sheer volume of practice. A few months ago I had my first go at ASP.NET Core, specifically Razor. Hadn't touched it for months, now I'm trying it again and I already f…
Indeed, switching context is fine and I think decent developer should be able to do it within first two weeks of ramping up. That's why I think it is a waste of time to go and learn the nitty gritty of all these platforms just for the sake of job interviews. Unless that skill is highly specialized like OpenGL/Vulkan API developer or something.