Remix.run Logo
▲ threatofrain 20 hours ago

Reading and understanding code? Or architecture? Reading code seems to be a very local concern, something that could be swapped out at will, sometimes with a whole new language and ecosystem.

▲timr 18 hours ago | parent [-]

I don't know, but if you don't write the code anymore, and you don't understand the code anymore -- at least to the extent of being able to quickly read and fix it -- then you certainly are not necessary.

So maybe we should try testing for that skill. This is not a hard thing to do, and there are many, many functional responsibilities and traits that a professional developer requires, which go beyond this.

Here are but a few, off the top of my head: spoken communication, written communication, time management, organization, focus, creativity, system design (aka architecture, as you suggest), planning.

It's always been painfully idiotic that we've used code golf for interviews, but the rapid advance of code robots has thrown it into sharp relief.