|
|
|
|
|
|
by rovr138
1641 days ago
|
|
|
I'll only comment on this, > Do you have examples of how hiring PhDs can go wrong? Not so much wrong, but there's a curve IMO. This is biased and based on my limited experience. Writing code or working on production systems sometimes they have trouble working the code bases. They can code, but don't necessarily have developed yet the skills to dig into code. I think everyone has this issue starting. There's also a big difference in code from academia to industry. Same with problems. We need a solution and a usable one. It doesn't have to be THE theoretical best thing always. It has to work. For example, you can't just not consider constants in complexities in production. Those constants take time. An example can be Netflix's challenge,
https://www.techdirt.com/articles/20120409/03412518422/why-n... ---- I don't necessarily agree with the generalists part. I think we all specialize over time and have some of the same issues changing language or even frameworks. We just don't have or know the best way of doing things within it yet. |
|
|