> You can assess an engineer based on how smart they sound in conversation, whether they use light mode VSCode or dark mode vim uhhhh. You sure about that? I'm

> You can assess an engineer based on how smart they sound in conversation, whether they use light mode VSCode or dark mode vim uhhhh. You sure about that? I'm not entirely convinced that the ide and the colour scheme make the dev. Sure, some of the most productive devs extensively use hotkeys and certain ides but I know of many devs that do those things and have incredible draw backs. One guy I know is a great dev but often misses the performance forest for the trees. The poor lad super optimised a process that was still painfully slow because it was doing a stupid thing (loading way more data than it needed at that time). It was stupid and all he achieved was doing a stupid thing incredibly quickly.