3 ms·
Yes. I posted that response this morning, then went sightseeing. Looks like I was completely misinterpreted. I would not judge people based solely on anything
by DanielBMarkham 18y ago
Yes. I posted that response this morning, then went sightseeing. Looks like I was completely misinterpreted.
I would not judge people based solely on anything -- race, creed, education, whatever. I would consider hiring another PdD in a minute.
If you put a gun to my head and asked for some kind of sweeping generalization, it would be that people who are very good at spending multiple years diving deep in one technical area are probably also people who are not generalists. And modern software development requires a wide-ranging skillset: negotiation, conflict resolution, interviewing, marketing, man-machine interfaces, graphical development, sales, consensus-building, etc. Oddly enough, I would even venture that most skills required by an agile team are not actually technology-related.
In addition (continuing me to make a generalization) at some point some people feel like they are "done" -- that they have learned enough and can rest on their laurels. Scrappy uneducated people never get this way, nor do hungry entrepreneur-types. People from other fields also see everything as new and for the first time. The guys I worked with seemed to think that their PhD had some kind of street credibility. Maybe it does with some, but in the environments I've been in it's more like "what have you done lately and what can you do for me?" And both of those questions are business questions and not technology ones.
- dhimes 18y agoAs I mulled my own cognitive processes, I speculated about the following possibility, which may apply more to small businesses than large: the academic/deep-solver (PhD or whatever) doesn't understand that the problem is often not well-defined enough in a business situation to warrant spending the resources for an omnipotent solution. The problem isn't really defined until the Market has a voice. Sometimes, the thing you thought was important isn't really important, the thing you blew off (or, in my most recent case, the thing I thought I was replacing the need for) turns out to still be quite important. Code it. Show it. Then, with luck, you'll know what the problem really is. At least, that's been my experience (but I'm still relatively new to this game).
- timr 18y ago"Looks like I was completely misinterpreted." How do you figure? You said that you've worked with a handful of CS PhDs, and you found them useless. It's a pretty straightforward interpretation.
- DanielBMarkham 18y agoyour opinion is that a PhD is not necessarily bad, but (based on your experience with a few people) that a PhD in computer science makes a person useless Nope. Hence the "being misinterpreted" statement. Seems like you want an argument. Go have it with somebody else.
- timr 18y agoI didn't start this thread. If you sincerely think I misinterpreted your words, you're more than welcome to explain your opinion with something more insightful than "nope". You may not have meant to say what you said, but that doesn't mean that my summary was wrong.