-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathLessons on Hiring Coders.txt
66 lines (33 loc) · 1.41 KB
/
Lessons on Hiring Coders.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
Lesson on Hiring People
What kind of person would you want to hire
for the coding job?
As for me, I would like the person who not
only could conquer ALL THE PROBLEMS in
"The Elements of Programming Interviews in
C++" by Adnan Aziz. We would also want them
to be able to pass tests in working on fictional
projects as a team. Basically, we will organize coders
so that they work in groups of two. They must
be of equivalent skill level or one of the worse
coders will weigh down the potential of the other
better coder. But what are the many,
many tests this does?
1. The coder does a great job of
archiving code AND DOCUMENTING CODE
THEY MADE IN THE PAST. The fictional
project will be designed to test this
in mind. Basically, the project will
offer coding problems similiar (but slightly
harder as they are allowed computers this
time) to the coding interview questions--
except these coding projects are actually
based on past coding projects the software
company has actually solved. Anyways,
the best coders will thus obviously be the
ones who have archived AND DOCUMENTED THEIR
CODE OUTSTANDINGLY because they will be able
to look at the similiar code they made in the
past and simply copy and paste the code
wherever necesssary.
Now, if only we could figure out how to distinguish
the best project managers and software architects?: