21–30 of 128 posts
"We have a lot of redheaded patients, we're looking for someone who has at least 7 years experience working with redheaded patients on a regular basis"
Earlier quoted context omitted.
Chances of people dying from my web app is super slim. Chances of people dying because I bladly wired their house is and it caught fire is a lot higher. Chances of me dying while developing my web app is super slim. Chances of someone frying themselves with wiring something up when they don't know how is a lot higher.
I will leave this right here for your education - https://www.bugsnag.com/blog/bug-day-ariane-5-disaster
Earlier quoted context omitted.
plumbers, electricians, civil engineers, architects, structural engineers, etc. All these occupations have licensing requirements. Why is software different?
> plumbers, electricians, civil engineers, architects, structural engineers, etc. All these occupations have licensing requirements. These are almost exclusively local regulations, not US national requirements, and certainly not international. So even if there were licensing, whose jurisdiction applies? What if you have distributed software development teams?
"We have a lot of redheaded patients, we're looking for someone who has at least 7 years experience working with redheaded patients on a regular basis"
Might apply to dermatologists. Maybe. Well, probably not.
I don't think doctors are a useful analogy for software developers. You mention doctors, then people are going to say "we need licensing for software developers" (which for the majority of programming jobs is silly IMO), and the conversation goes off the rails. Doctors are an unusual profession, leave it at that.
plumbers, electricians, civil engineers, architects, structural engineers, etc. All these occupations have licensing requirements. Why is software different?
There are plenty of journeyman carpenters that do not have a license, this is not a problem as long as they work for a company that is licensed.
On the other hand, if software engineers were interviewed like doctors, anyone who didn’t have a U.S. graduate degree would be immediately rejected. Anyone with great experience in another country would be immediately rejected. That is most of the good doctors in the world! The doctor interviewing process is simplified by rejecting the vast majority of qualified candidates before even interviewing them. I think the f…
It's a myth that you can work without a degree, you'd never get a job interview in the first place. Seems to be mostly a US myth by the way, makes sense because degrees are crazy expensive there.
Earlier quoted context omitted.
> plumbers, electricians, civil engineers, architects, structural engineers, etc. All these occupations have licensing requirements. These are almost exclusively local regulations, not US national requirements, and certainly not international. So even if there were licensing, whose jurisdiction applies? What if you have distributed software development teams?
This is a solved problem per our tax laws. Just because you write code that runs on a server in another state, doesn't mean you pay the taxes in that state.
So in one sense, it's a "solved problem", with the solution being that licensing requirements would be dramatically different based on locality, but in the sense that people want — a uniform standard for hiring software developers — it's not solved at all.
This doctor vs programmer comparison would also be more useful if there was an order of magnitude difference in effectiveness of doctors. Compare that with the order of magnitude difference in the utility of the systems that programmers can build. There are no real "10x" doctors except for those with medical + management training that can do things like set up a new hospital in an impoverished country and revamp their medical system. But it's much more likely to have programmers that can build systems with many orders of magnitude difference in terms of QPS or a similar utility metric. That is, there is no version of Big-O notation for doctors that matters as much as the big O notation for programmers.