3 ms·

That is an interesting question. How are law and medicine different than CS career-wise? A couple additional thoughts, not intended to be exhaustive: * CS is n

by pacala 6y ago

That is an interesting question. How are law and medicine different than CS career-wise? A couple additional thoughts, not intended to be exhaustive: * CS is notorious for its solitary aspect. Stare at a screen juggling abstractions for hours on end. * CS is notorious for lack of career paths. Between ageism and outsourcing, once you hit 40, the perception is you are relegated to the bottom of the pile.

humanrebar 6y ago
> CS is notorious for its solitary aspect. Stare at a screen juggling abstractions for hours on end. It's also false. Software is inherently collaborative, especially at senior levels. And it will likely stay that way as long as the job looks a lot like consulting due to lack of defined sub-specialities. There is no technician specializing in particular forms of testing in the software industry. In medicine, there is a whole host of these specialities. Point being "it's your job, so figure it out" is the rule. And that means working out not just solutions but well defined problems with peers, customers, superiors, and other stakeholders. It's possible to do interesting Computer Science in relative isolation, but good luck making a career out if it without collaboration, publication, teaching, and other inherently social activities. You might know all this, but I think it's important for the industry to push back on the nerd-bro in a basement imagery since it's absolutely not what actually happens.
- pacala 6y ago
  Of course there is some social aspect to CS. That being said, comparatively, the interaction loop is waaay more abstract. Just walk into a medical practice vs a software engineering office. As a medical professional, you get to interact face to face with several people every day, and have a direct observable positive impact in their lives. As a CS professional, you spend half your waking time dealing with or dishing out style guide feedback nitpicks via email / irc / github [FAANG experience], interacting remotely with funny little avatars. You very rarely directly experience the impact of your work, and the impact itself is quite a bit less clear cut positive.

by pacala 6y ago

humanrebar 6y ago

> CS is notorious for its solitary aspect. Stare at a screen juggling abstractions for hours on end. It's also false. Software is inherently collaborative, especially at senior levels. And it will likely stay that way as long as the job looks a lot like consulting due to lack of defined sub-specialities. There is no technician specializing in particular forms of testing in the software industry. In medicine, there is a whole host of these specialities. Point being "it's your job, so figure it out" is the rule. And that means working out not just solutions but well defined problems with peers, customers, superiors, and other stakeholders. It's possible to do interesting Computer Science in relative isolation, but good luck making a career out if it without collaboration, publication, teaching, and other inherently social activities. You might know all this, but I think it's important for the industry to push back on the nerd-bro in a basement imagery since it's absolutely not what actually happens.

pacala 6y ago
Of course there is some social aspect to CS. That being said, comparatively, the interaction loop is waaay more abstract. Just walk into a medical practice vs a software engineering office. As a medical professional, you get to interact face to face with several people every day, and have a direct observable positive impact in their lives. As a CS professional, you spend half your waking time dealing with or dishing out style guide feedback nitpicks via email / irc / github [FAANG experience], interacting remotely with funny little avatars. You very rarely directly experience the impact of your work, and the impact itself is quite a bit less clear cut positive.