Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
If you think it is too easy for senior devs then you can add more complexity.
It is the concept and what it looks at that is more important.
Instead of us testing if they can remember some obscure algorithm (that you would just look up) you can assess their thought process.
If you read the article you will see that the actual problems are not what is being tested, instead we are testing:
their thought processes,
refactoring,
thinking about extensibility,
following instructions and briefs and knowing where to ask questions etc.
These are the skills that matter in a team, I don't care if you can write a "travelling salesman problem" solve from memory, I just care that you can order your thoughts into a logical path to complete a given challenge in the real world and create code that is easy to maintain.
Also, it is just a concept, you can make it as difficult as you want by just adding harder requirements after point 8.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Yeah, and that is half the issue as it skews the thought process!
It is always fun seeing how people spend months practicing coding interview problems who have been developing for years as it isn't what they do each day!
I always imagine it to be like a lorry driver being asked how to replace a clutch...kind of related but doesn't tell you how good they are at driving and a skill they will probably never need to use! π€£
What kind of question would be good to know interviewees problem solving capability in about an hour?
A basis for a coding interview using "FizzBuzz" onlyβ- 8 challenges for beginners AND Pros [with a twist for Pros! π±]
InHuOfficial γ» Jul 11 γ» 13 min read
The concept is to build upon previous bits to show a persons thought process and how they organise (and reorganise) code.
Needs some refinement but I think a concept like this is way better.
You can't have such basic one for intermediate or senior role
If you think it is too easy for senior devs then you can add more complexity.
It is the concept and what it looks at that is more important.
Instead of us testing if they can remember some obscure algorithm (that you would just look up) you can assess their thought process.
If you read the article you will see that the actual problems are not what is being tested, instead we are testing:
These are the skills that matter in a team, I don't care if you can write a "travelling salesman problem" solve from memory, I just care that you can order your thoughts into a logical path to complete a given challenge in the real world and create code that is easy to maintain.
Also, it is just a concept, you can make it as difficult as you want by just adding harder requirements after point 8.
To be honest I never liked CP
My leetcode rating it 1 star
But most tech companies will either demand a degree which I don't have or good cp skills
Yeah, and that is half the issue as it skews the thought process!
It is always fun seeing how people spend months practicing coding interview problems who have been developing for years as it isn't what they do each day!
I always imagine it to be like a lorry driver being asked how to replace a clutch...kind of related but doesn't tell you how good they are at driving and a skill they will probably never need to use! π€£
Maybe some day it will change