Timeline for How do we recruit junior software developers in an age where everybody studies for the interview?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 2, 2019 at 12:07 | comment | added | Matsemann |
Agree, OP also wrote: Now, this would of course not be a problem if knowledge of those problems is what we are looking for ... except, that isn't what we are looking for. Which even further proves the questions they ask are completely pointless
|
|
| Dec 28, 2018 at 14:36 | comment | added | Conor Mancone | @jpmc26 I would say that this answer more clearly identifies the root of the problem. The OP is clearly asking the wrong questions. Sure, the final suggestion is more or less the same for both of these answers, but stopping to ask the OP "why are you asking your current questions?" is a very important addition. | |
| Dec 28, 2018 at 5:28 | comment | added | Alexander O'Mara | They are somewhat similar in suggested solution. I thought it was important to address why their current method isn't testing what they actually wanted though, and suggest that new tests could be as simple as using recent challenges programmers have faced, rather than inventing new contrived tests. | |
| Dec 28, 2018 at 5:13 | comment | added | jpmc26 | This answer does not appear to differ significantly from user1666620's. | |
| Dec 27, 2018 at 23:20 | review | First posts | |||
| Dec 28, 2018 at 1:21 | |||||
| Dec 27, 2018 at 23:18 | history | answered | Alexander O'Mara | CC BY-SA 4.0 |