3 ms·
>he kind of developer who writes code quickly may also be the kind of developer who jumps to conclusions too quickly I'm the opposite of this, but when I wante
by VirusNewbie 2y ago
>he kind of developer who writes code quickly may also be the kind of developer who jumps to conclusions too quickly
I'm the opposite of this, but when I wanted a really high paying job, I just practiced a bunch to code quickly. That was actually my biggest hurdle, sometimes I'd understand the problem but I couldn't bang out actual working code fast enough.
Other times I'd get so nervous that I wouldn't have time to code that I'd stumble on the thinking part. Once I deliberately practiced for speed, I was much calmer in interviews.
And now I have a really high paying job. shrug. Now, it's not the best at finding outright geniuses, but making people solve slightly harder than trivial coding questions is a pretty consistent filter for people who can't code.
If you're good at coding and you can't do it, then it's just a matter of practicing a bit.
- jongjong 2y agoYes but what kinds of people have the time to practice puzzle solving? Not everyone. For example I've been coding for 10 years, I used to be good at solving puzzles under time constraints but I'm not as good at it anymore because I prioritized practical architecture and other code design skills. I'm a much better coder today by all relevant metrics. My problem is that I sometimes run out of time during the tech tests. It's arbitrary... Sometimes I get lucky with the questions sometimes not. An unfamiliar problem will take longer to solve.
- VirusNewbie 2y ago>Yes but what kinds of people have the time to practice puzzle solving? The kind who want to get an extra 100 - 200k a year in RSUs?