Slashdot Mirror
Switching from Another Industry to Engineering/CS?
WomensHealth asks: "I am a physician, but contemplating a career change perhaps 5 to 10 years down the road. In addition to medicine, what I've always loved is computers and technology, and I think I have a pretty good appreciation for both. What tips could computer industry insiders offer to one who is willing to pursue an independent educational path towards a career in a Computer Science field? MIT's OpenCourseWare seems well put-together, though one can't get a degree using it. How can an old newcomer break into the industry?"
You might go into genetic research, although that will probably be sourced offshore, too.
"Computers are useless. They can only give you answers."
-- Pablo Picasso
I really hate to be so blunt - but where I'm from we're severely lacking Medical Doctors. Here in Ontario, we really need you people.
Please, stick with your current occupation. You're saving lives there, and I doubt you could say the same in an IT field.
.
Go down to your local Fry's and buy a nice shiny computer. Use the computer to visit the GNU website and take a look at the projects that look like they need some help. Download the code and start working on it using Cygwin tools or Linux, if you've installed it.
Forget about making money in the industry, you're much better off getting a degree in plumbing, the pay is better and the hours are better.
I have been pwned because my
From someone who has been in the industry for 10 years: the answer is...don't. This is a dead end field now, especially with competition from markets that can support low wages and people willing to give away their work for free.
It was once a good field to be in, but has now become so devalued that I cannot recommend it.
Go ahead and do it!! Instead of doing something like certification courses (CCNA, MSCE, etc.) that might or might not be accepted, try and get into a MS degree program somewhere. And to do something like this is definitely possible... from where I worked at a couple of years ago, I had one person in my group who went from being a heart surgeon to a software engineer and someone else who went from a city cop to a chip designer. Sure, its not easy but at the end of the day, you will have what counts.
It's too late for me! I for one am looking to be out of IT in 5yrs. Seriously, why throw away a medical education for an industry of questionable future and even more questionable ethics and morality? In my opinion, if you sold real estate like software is sold, ou would be in prison. If you sold used cars like software was sold, you would be in prison.
my $.02
putting the 'B' in LGBTQ+
If your training leads you to a career that can be done from offsite, that same carreer is in danger of being offshored.
There is no business difference between someone who telecommutes from India or Indiana.
comment directly in my journal
The one advantage that you do have is in-depth knowledge about a potentially lucrative customer niche: medicine. Consider leveraging that to specify, maybe even design software and systems to help medical people.
You might be able to code up some demos and do some usability testing, but (IMHO) you ought to resist the tempation to try to implement production systems. Quality is important, and experienced developers automatically deal with issues that you wouldn't even think of for years to come. Hire quality people and let them make you rich!
I hate to mention politics, but it has allot to do with the current problem.
I voted for Bush, but he has done nothing for the middle class workers losing jobs to outsourcing sweatshops overseas.
This is the reason why Bush will not be reelected.
This question is insulting.
How would you feel if you got the following question from a patient?
[pretentious diatribe deleted]
Unfortunately, the analogy is false. IT doesn't kill or save enough people, so there's no rigorous screening process for people entering the field. There is no 7-8 years of proving ground and education before being released upon the masses.
The fact is that kids out of HS and smart people all around the world are picking up IT like loose change.
Here's some real advice for the original poster: Some of the hottest IT jobs right now are probably...tada, health-related industries. Look around what you do RIGHT NOW and look at what things could be done better and more efficiently using computers. Develop some software to do so and you can make a mint. Hundreds of successful startups do just that--recognize an inefficiency in the medical system and fill a specific niche. If you want to break into the industry, no need to learn all the coding yourself--just find some smart coders, show them the inefficiency and give them some ideas how to fix it, spread around a little seed money and voila, you're a mogul.
How can an old newcomer break into the industry?
It seems plenty of other slashdotters have beat me to the "Move to India" suggestion.
But realistically, the best way to get into the computer/tech industry is to get into one of the high profit vertical markets. Great examples of these are Enterprise Storage (IBM, EMC, HP, Sun, Hitachi), Supercomputing (HP, IBM, SGI), maybe even VOIP or biometric security. Additionally, consulting services which are wrapped around the aforementioned markets are particularly lucrative.
You basically want to avoid like the plague any job which can be easily outsourced to India or another cheap labor market. Programmers, Call center workers, WWW operations are a few examples.
Also, dime-a-dozen certifications like MCSE and MCP should be avoided as they are usually costly for you to get (if you are paying for them yourself) but provide little or no real world benefit to you.
Just my two cents.
I'd rather be a conservative nutjob than a liberal with no nuts and no job.
It's not possible to be talented and successful without a lot of hard work and study, regardless of licensing. Asking "How can I take the shortcut route to being good at thie profession?" is insulting.
First of all, the poster wasn't asking about "IT" or even "programming", they were asking about Computer Science. And Computer Science does kill people. Have you ever read the Risks digest? There are hundreds examples there.
The fact that licensing is not currently required is another story... for some jobs, I think it should be. But regardless of what the licensing situation is, it is unrealistic, and frankly insulting, to expect a shortcut into become serious and good at something.
"Kids out of HS", as you say, pick up IT like loose change. What does that mean, that they can write a VB app and put together a network? Would you trust such a kid out of HS to write software that runs the autopilot on a 747, or the heart monitor in your hospital, or for that matter the firmware of your cell phone?
I'm all for it. The typical slashdotter probably wouldn't be though. But bear in mind that many of the slashdot crowd are IT professionals, a single occupation within a greater sphere that has seen significant job losses. The sad reality of computers these days is that if you want to do something with computers, the best way to get a job is to know something about what you're doing with them.. I believe this was said by Joel of JoelOnSoftware or some such semiluminary.
Well, as a physician, you've got some specialized knowledge that will come in handy from time to time. I'm sure you've heard plenty about biotech. I've seen some of these DNA "computers" and chips, and it seems very wasteful. Grow specimen, extract and treat dna, splash on a grid with transverse dna's and call it a computation. Then record the data and throw it away. This is just one example of the biotech oddities that seperate the field from your average HTTP server. There's all sorts of places to work. Merck, Eli Lilly, etc. Having a MD with some working knowledge of computer programming will get you further than having a degree in computer programming and a working knowledge of human physiology.
Your best bet is to start writing programs for yourself, and maybe design a few gui tools to put on top of them. Basically build a working portfolio that demonstrates you can write in perl, SQL or whatever, then apply. Or maybe you will find that a few of your own programs are marketable to your friends. I hear many doctors enjoy PDAs and related software. If your a general practicioner, you might try thinking about what sort of software would make your practice faster, more reliable or more cost effective. By all means, read up on HIPAA and the sorts of laws regulating how software should treat patient data. Maybe buy a pda and a wireless reciever and learn how to interface software from the pda to a database over the wireless in a safe, secure manner.
Learning to program is not that difficult. Some languages make it more obscure than others, and some languages are built for more specific domains than others, but here at KSU we only really have three "how to program" type classes of varying difficulty before you begin to learn how to specify WHAT you should program, be it a database, an operating system or a 3d renderer.
I Browse at +4 Flamebait
Open Source Sysadmin
1. Learn to program
2. ?? (*see below)
3. Profit!
*In your profession, you probably can find a need that because you've worked in the trenches you can fill better then any programmer could. Programming is not something you can learn overnight, but is more like a talent, like playing the piano. Figure out the niche that you can fill, and make a program to handle it. Make it open source (GPL) and start using it. Talk it up among your doctor friends and see if they are interested. Others may join in, and start asking for changes that you haven't anticipated. At this point you can start charging for enhancements. Since you are the expert in this program you are the one contacted. Get some rightups in medical journels and you are on your programming way.
I would feel honored, not insulted. Same as I feel about someone asking about entering the computer industry. Curiousity is nothing to be offended by. Just because they have little or no experience doesn't mean they have little or no appreciation and respect for what you do.
As for the question, my recommendations are: 1) Have plenty of reserve cash. I hope the industry is better in 5 or 10 years, but even if it is you'll need money while you train and take those entry level jobs. 2) Experience is better than certifications. You often need the latter before anyone will let you get the former, but if anyone offers you ANY job remotely related to the field you're interested in, take it. On the job experience builds your skills and your contacts. 3) Combine your interests. The things that stand out most on your resume are not your certifications or even your IT experience (though both are often required), but the other interesting things about you. For instance, I entered IT from a background as a high school teacher. Know what? Most employers find that background tremendously valuable and look to me as a trainer.
Best of luck to you!
-madgeorge
An understanding of computers on it's own is worthless. It is the understanding of computers and how to make use of them to DO SOMETHING USEFUL that is the rare skill. This is what the readers of Slashdot don't understand.
If you have a knowledge of Medicine and Computers, then you use the COMBINED knowledge to advance the state of the tools that doctors use. If you have a knowledge of physics and computers, you help design models of how the universe works. If you have a knowledge of how accounting works, then you design software that helps bring Enron to it's knees. The point in this is that CS and IT is WORTHLESS unless you understand what the technology is used for, and as such, in the CS field you have as much value if not more than you did in you own field. This is because you UNDERSTAND the field you could help. The appropriate area of work is called "product management."
There is an old phrase: If you give a man a fish, you feed him for a day, if you teach a man how to fish, you feed him for a lifetime. This is the way with computers--if you have the knowledge of how things SHOULD be done, and help make that a reality, you solve the problem for a lifetime for everybody involved.
People like you ARE the ones making progress in the use of computers, not those that graduate in CS. Why? Because you help embody the knowledge of what you have learned into the systems that will be used in the future.
Erik
If you enjoy computers then play with them. You will lose your joy if you become a professional. I like eating ice cream but I don't think I'd enjoy eating ice cream if I worked in an ice cream factory.
This business is harsh. I don't know what medicine is like but the IT industry is not pleasent anymore. It was at one time when the field was filled with brilliant innovators but now it's just shit.
Finally any doctor I know drives a nicer car, has a better house and a better looking wife then any computer professional I know.
Don't do it, you'll regret it later.
War is necrophilia.
I know I'm going to make some enemies with this post, but I seriously urge you all, who think that it's bad that jobs are going to India, to consider the benefits of offshoring IT jobs.
By having cheaper labor do the same work and produce equally good or better products and services is a good thing. Remember your college economics class? Comparative Advantange? It's important for a nation's economy to do what it does best. Just as the poster asked whether or not she should get into the computer science field, I would say, if you like it and you think you will be better at it than medicine, then by all means, go for it.
By having people do what they do best, it allows for specializiation and the way corporations work the way they do today. Specialization allows more output from the same input by increasing the productivity of workers. Similarly, specialization applies to the global level and when nations specialize in one service or good, that is better for the entire global economy. Just think back to the 70s and 80s when the auto industry was screaming bloody murder over the import of cheaper and better made Japanese cars. Americans learned to respond to that. Similarly, the currently shrinking job market in the IT field is not something to be afraid of. There are plenty of problems that require solving in the technological sciences involving computers that currently displaced employees can help solve and this is an overall benefit to global society. Yes, there will be a short-run hard hit to people at home, but allowing free trade is a good thing. And in this case, it's the free trade of jobs in the computer industry. But remember, in the long run, it's in the best interest of everyone.
The person who posed the question said CS/Engineering, and all you guys seem to have heard is 'IT'.
'IT' has as much to do with Computer Science/Engineering as the guy who changes the oil in your car has to do with Automotive Engineering.
It finally 'got to me' this far down in reading the comments. Sorry about that.
---
The poster was asking about a career change not about the financial incentive to do so Doing something some one loves is more apt to produce results than to do it for the money. Most people in the Medical field will tell you often the money really is not there. Perhaps they are looking at a career change for retirement or any number of other reasons. Just answer the question rather than imagining what the motivations are...
I wish I had never taken my engineering degree. It is the biggest regret of my life. I'm doing some consulting and have a few business ideas, but it's very difficult to get funding for what I want because of the climate for tech. My alma mater's graduating EE class last year had very few employment opportunities, and what few were there were either extremely low paying or extremely demanding field work (16 hour days 6 days a week). A friend who's a vice-principal of a school wanted me to come in and talk to her students last year about technology careers, and I told her I couldn't conscionably do it because the climate is so awful and unlikely to change that I'd recommend either medicine or trades instead of what I took.
There are tons of jobs for doctors here in Canada and the US. Unlike the vast majority of engineering and CS jobs, medical diagnoses will never be outsourced. Heck, take a small business course and get creative with what you've got now and market your services uniquely as a GP or whatever else you want to do. Without health, we have nothing. That's why your job is likely the fundamentally most important job in our society, and why doctors will be the last people on earth out of work.
There's some issues I read over and over...
"Programming! Programming!" - Any quality CS program is only about 1/3rd programming related. 1/3rd is theory, and the other 1/3rd is hardware architecture. Usually you'll have a few advanced classes which bring it all together (like operating systems design). A well educated computer scientist can switch languages with ease depending on the needs of the work and learn new ones quickly. In the CS world, programming is just a means to an end. I'm 1 semester shy of graduating with a degree in it and doing the programming is perhaps the least interesting part that I thankfully, spend little time in. I'm more interested in solving problems with *design* than typing away lines of code.
"There's no jobs!" - Yeah. Maybe if you don't have a CS degree which focuses on the *SCIENCE* part of it. There is a quite a demand for people in the engineering and scientific world who can design (as opposed to simply "program") advanced algorithms and computation software. Even if your speciality isn't scientific computing there is still a large number of jobs waiting for people with CS degrees out of well known schools in a variety of areas. IBM's making a big push for CS grads.
"*somethingsomething* IT! " - CS is *not* IT. Its like comparing the doctor's receptionist to the doctor. I'm not belittling the receptionist or the IT people - both the doctors and the CS folks need their records/networks organized and maintained with skill - but they do fundamentally different things.
-
Computer programming is something you can learn to do adequately well in your spare time, sufficient to build small but very useful systems.
Software engineering is (or should be, the term is widely bandied around but not very meaningfully sometimes) the process of building large software systems on time, on budget, and to specified levels of quality and reliability - at least in theory.
Computer science is the theoretical study of computing - what they can and can't do, how long it takes to do it, and trying to make them do the things they can't current do very well! It's conducted at universities and research labs, mostly by people with or seeking PhDs. Much of it is almost a branch of mathematics.
If you're already a practising physician, 5-10 years from now it will be a little late for you to be considering becoming a full-on computer science researcher in a field that doesn't take advantage of your background.
You could certainly learn to become a competant programmer in your spare time, but it would take another degree and more professional experience to become a fully-fledged software engineer. As you've heard, there's a lot of doom and gloom at the moment about job prospects in that field, mainly because of the outsourcing boom. Who knows what the demand will be like in 10 years. However, demand for doctors is virtually guaranteed to increase over the next decade or two as the population ages, so I wouldn't be considering the move if job security is at all important.
If you are serious about a career change, I'd be exploring the possibilities of working on medical technology. From what I hear, doctors are notoriously clueless when it comes to information technology, so somebody who can translate between medical jargon and IT jargon is going to be enormously valuable and have a very interesting career, no matter what side of the fence they sit on.
Any sufficiently advanced technology is indistinguishable from a rigged demo
--Andy Finkel (J. Klass?)
They preach to engineers that they should be well-rounded, and know a little bit of everything -- math, physics, yadda yadda yadda. But if you're joining late in the game, just focus on the important stuff:
For math, I'd definitely start with discrete mathematics. Work through it thorougly -- not only are its concepts like trees, graphs, recurrences, etc. immediately applicable to CS, but you should get a good feel for other elements of formal mathematics you'll need later, such as formal proofs and mathematical notation. If you really love discrete math after doing this, I'd suggest you pick up Knuth's book Concrete Mathematics -- but not many people would be ready to make that jump. Another branch of mathematics you might want to pursue is logic -- handy for AI, and it really puts you in a mindset you'll find useful in CS. (A shameless plug for my logic professor's awesome book is here.)
Then onto the computer science portion of our program: I don't know the extent to which you know programming, but assuming something minimal, start off by learning how to program in a scripting language. I recommend either Perl or Python (or both). If you're looking to apply your medical skills to computing, these languages are key -- in fact, today I turned down a job to hack on the Human Genome Project at my university. The preferred languages of applicants? Perl, C++, Java, and Python. So you'd score two of the four languages right there. Then, pick up a book on Algorithms, and start reading it (such as CLR). Hopefully, your brief foray into programming and your exposure to math by way of discrete and logic will make that read easy and enjoyable.
Where from there? Pick up a more widespread language, such as C++ or Java. Then pick a specialization in Computer Science that sounds interesting to you, and start reading about it -- such as networking, databases, computer architecture, etc. I can't emphasize enough how much a book can teach you -- a book can be all you need to succeed in many classes.
I know the above outline of what to learn is not found in most (all?) colleges. It's not what I'm going through right now at my university. But right now, off the top of my head, that's the best fast-track program I can think of.
Best of luck to ya,
shadowmatter
Spark, meet tinder. Tinder, spark.
Now that that's out of the way: if you're considering a schooling method other than self-instruction, you're not going to be fit for the industry anyway, so don't even bother. Seriously - people go to school for things like IT and CS, sure, but just that won't do a thing for a person. CS requires one be always updating their skills; if you're just getting into the field at 40+ (I figure this number from the idea that you graduated college at 23ish, the spen 8 more years in school after that, plus whatever time you needed to become an established physician who is already considering a career change) and doing so by going back to school, chances are you've not got the right mindset to be successful in the field, especially considering the atmsophere of the industry for the last 3ish years.
Have you been under a rock for the last 3 years, I wonder? Seriously. I can't but almost consider this some sort of mockery of slashdot, and possibly simply a joke. You're a physician. You rob people of immense amounts of money (usually paid for by insurance). Your job is dependable - people will always get ill. You could live a comfortable live and spend your money on expensive gadgets and new server racks for your toys - and do it on your leasure, for enjoyment. But instead you'd rather make a pittance in your old age, at risk of being fired or dismissed for any number of reasons, so as to get to work long hours under unkind managers? It seems to me that the doctor tends to be at, or near, the top, in many situations. Seems a bit more preferable.
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
Addendum:
:) Even forensics could combine the two successfully.
Most networks/databases in hospitals are designed by techs who really don't understand how hospitals function. Also, most hospitals are VERY behind as far as computer systems go.
You have the advantage of previously being an end user. You would have tremendous insight in the design and implementation of said systems, how they should operate... right down to the software used. Especially with HIPPA regulations, the networks are ill-conceived and insecure, or unuser-friendly. You could help remedy that.
Imagining and physics based medicine have really cool toys
Hang with the IT department and see what they do, and figure out ways to improve the current system.
Medicine has been rather sketchy as far as cohesiveness of all the technical aspects; there's lots of ground to cover. With a little bit of moxie, and a bit of creativity, you could literally turn the two into damn near anything you wanted.
Here's a medical analogy for you.
;/
The situation in the computer industry is like medicine would be as if every kid who had dissected some fetal pigs decided to hang out a shingle and become an obstetrician.
You're looking at replacing a secure, varied and financially extremely rewarding field with a field which is insecure, hypersaturated, and arguably can be done by someone with very little education.
Not only that but IS work lends itself to ruts. Wherever you work, you're going to be learning an API or a network system, and then you're going to be writing for or supporting that API or network, until you get another job, where you could very well be doing exactly the same thing.
If you're interested in spending your time in overcrowded cubicle farms full of stressed, angry, reclusive programmers who live in constant fear that their jobs are going to be given to retrained bricklayers from bloody Pakistan, you're headed in the right direction!
Oddly enough, I'm in a position now where I can run screaming from the bloated tech industry, and I'm back in college getting ready for med school.
The only way your idea is not utterly BONKERS is if you want to somehow use your medical skill to get into something like bioinformatics where the money is potentially gigantic for doctors who have technical ability.
Here's what the computer industry is like right now. You have a lot of people who are very experienced and good at what they do. Then you have numerous carpetbagging amateurs who have installed kiddie Linux a few times, are good at bullshit, and have wormed themselves into positions of responsibility. It's almost like a kind of Ponzi scheme.
That's much of the reason why the industry lost a lot of its credibility. That's much of the reason why the industry started asking "Why are we paying this yoyo $120 an hour when Patel in Calcutta says that he can get the job done for rupees on the dollar?"
Look very very carefully at this before you do it. You've got numerous people here-- who should know-- telling you things like "Abandon hope all ye who enter here." This is no joke.
Sorry to rant but I'm sure most of ya all know what I'm talking about
Intolerance for ambiguity is the mark of the authoritarian personality.
I wouldn't recommend it... There's a great need for good physicians and once you start messing with computers for 60+ hr/wk - well let's just say that after the original excitement after a couple of months it becomes a pain - my dad changed to IT from a stat professor and that was his experience. I've always liked computers and I want to keep liking computers so I resolved to enter a non-CS engineering field instead and treat as a hobby - with your income as a physician you could afford to construct a geek's paradise - build your own network at home - maintain a couple of servers (WWW/POP/NIS/DNS/SAMBA - a DEC alpha, a sparc, an itanium, opteron,xeon) and you'll still have lots you can learn and can still enjoy computers.
First off I should mention that this is nothing more than a plug. Dalhousie university (Halifax, Nova Scotia, Canada) has just started a graduate program in Medical informatics. Medical informatics is basically the science of using mathematics and computers to data mine medical information for useful results. This is particularly relevant to this situation since the ideal candidates for this program are people with a medical background. People who can look at the data and form some sort of understanding of what it means in the real world. I know at the moment Dalhousie is the only Canadian school to offer such a program though I do believe there are a few American schools offering similar programs. Beyond that I don't know who else offers such a program.
It is also worth noting that Dalhousie Comp sci has just aquired Jon Borwein who is one of the worlds formost experts in experimental mathematics and just happens to have a history with several of the developers of the Medical informatics progam. It is unclear if he will be involved with the program but he will certainly be teaching courses at Dal. Probably worth looking into.
I would say the best thing for you to do would be to specialize in creating hardware software that would have medical implications.
you don't need a degree to "break into the industry"... if you must get a degree get an MBA or something like that... in any case, try to become an entrepreneur rather than a salaried worker... if you spot an opportunity, no matter how small, you can go for it without a degree... if you can provide a service or a product for a reasonable price, then the market really doesn't care about degrees...
is DON'T. Here are a few reasons why you really ought NOT to get a tech degree / persue a tech career: ... just for 10 minutes". As a tech, you're expected to save your neighbors from themselves continuously. ... as a CAREER path in this day and age, though ... you really don't need the hassle. You served your "8-years-of-hell" already going through med school; no need to repeat it with a career. ... but it's not seen that way these days.
:( Sure, I have Gray's Anatomy, have done dissection, and know what bursae are ... but guess what? That doesn't get me a damn dime.
... it was crazy.
* As an MD, your next-door neighbors don't really expect you to "just pop over and check out Bob's heart a bit
* As an MD, your time is respected (see above).
* As an MD, you're employable.
* As an MD, it pretty much stands that you're in a respectable profession with reasonable people. The same assumptions will not neccessarily be made in tech.
* As an MD, if the patient dies, people are typically understanding. As a tech, if you can't revive someone's 80086 to run Windows XP PRO, then YOU SUCK.
* As an MD, you'll see the field saturated with Indian and Pakistani folks. As a tech, you'll see the field cornered with Indian and Pakastani folks(1).
* As a HOBBY, computers are great and are quite rewarding
* If you're looking for some Mad Money / Retirement Money, look elsewhere. I personally ended up coming back to school for advanced degrees rather than go work in Texas for $28,000/year as a professional.
* Respect, respect, respect. MD == "professional". Engineer/IT Person == "professional" also
G'luck. I personally wish that I'd have done what you did (med school and kept computing as a HOBBY) rather than the other way around.
N
(1) I have nothing against either; I worked for/with Pakastanis in a mom-and-pop shop in the mid-90s
One of my clients/partners sounds like he could be you. :-) My partner is really anoyed about the materialistic extremeties in todays medical world and he thrives to evade it by that combination of strategies: True Continous Medical Education (you see, I know the buzzwords allready :-) ) and part-time dealing with a field he has a hobbyists interest for. Just the right thing for you too, I'd suggest. ;-) who knows what he's talking about and also has some business and social skills. Note that I'm originally an artist and also come from another field than CS/IT. When you start a business, know where your power lies and learn to pass on the parts that you're not good in, even if you would like to do everything yourself. That's one part of success. Best of luck to you.
He's a top-notch dermatologist and has worked as a consultant for the most advanced imaging system available for dermatology - one that can automatically diagnose dermal anomalies such as skin cancer. He's got a company that expertises in medical E-Learning for medical personell and works for various medical organizations and the pharma industry.
I'd suggest that if you want to study because it interests you, get used to the idea of studying for fun. When you've got your degree you can still decide what to do with it.
On the other hand, I'd suggest you either stick with your jobs which has something around a bazillion advantages over CS and IT or you combine both with medical consulting for pharma companies and other organizationhs in IT related medical projects. Or medical related IT projects. You could even do it parttime until your business is going.
As for my client/partner, he hasn't got a CS degree but he spends 2 days a week dealing with the field and it's geeks (me). His Webdesign is horrid and I'm having a hard time talking him out of it, but his medicine skill and expertise combined with my computer expertise gets us to sit together with the really big boys in pharmacy, who have so much money they light up their chimney with 500 Euro bills.
Bottom line:
Get into _one_ field that interrests you in CS/IT that you think could go well with what you've got allready. If you've got the brains you won't need a degreed - don't forget: medicine has been around since 10000 years, but computerwise we're still in a stone age, with maybe 100 years of knowlege in the field! It's all about brains and what ideas _you_ come up with. Technologies change and evolve on a half-year basis. Not a good enviroment for a usefull degree, if you ask me.
My partner and I use open source + custom code only and we're 2 people competing and outrunning companies with 100 employees and more - I'd strongly suggest you go that way too. When you're firm enough get yourself a contractor/partner like me
We suffer more in our imagination than in reality. - Seneca
Ok, you may switch to IT, just be carefull while choosing the thing you'll be doing.
For your situation, stay away from software development "as a developer". There are much better roles for you.
I am currently working in a software company, and our expertise is on medical sector. We provide many solutions, and currently i am working in a health provision system as a developer. We have 3 or 4 doctors in our firm. This number changes from time to time, as we hire some doctors as consultants.The doctors are very important for us, since as developers, we can build the system, but we have very little information about the processes and data the system must use. When our software must offer a medicine instead of another, the logic that's used is very, very complex.(international medicine indexes, and many sector spesific info..) And the doctors are the only guys we can consult about these kind of stuff. Try to design a user interface for a doctor, and you'll have a hard time to figure out what should be on the screen for results of say a surgery.
If you are skilled in programming, or want to be so, work on it, that's fine. But instead of trying to be a programmer, try to be the guy who interacts with customers and the technical guys in the company. Believe me, you'll be important for them..
This way, you can use your domain spesific information, and you'll be more secure against the cycles in the industry. It's much harder to find a doctor with IT information, than to find a programmer without sector spesific info.Developers come and go, but you'll have a better chance of staying where you are.
Yeah well he has a point though... these "inside jokes" do get old at some point. I mean, come on... there's like thousands of 'em 1-2-3 profit jokes by now or something, attached to every story for too long to remember.
What's also funny to notice is that it's usually the still pretty "novice" users (like uid 400000+) who label them as "inside jokes" and still laugh about them. To *you* perhaps, it's an inside joke, because that's how *you* got to know slashdot. That's how *you* got, at least in your head, connected to this "community" with all these friends and stuff.
To others, however, it pretty much seems like the quality of the discussion has been deteriorating with each year's new load of "insiders", who keep recycling the shitty lame jokes they saw some trolls make when they first hit slahsdot. Impressed with all the "funnyness", they are apt to adapt and adopt.
Together it kinda reminds me of the way we used to keep "connected" as a social group in high school. Like make the same old joke in a different way, laugh about it and know you're all on good terms and such. You know? Like needing a family or something.
We solved that by getting a life.
There's a lesson for you somewhere in there.
I switched from medicine to computer science in order to scratch a long standing itch, got a CS degree and worked for 10 years in the field. I am now back in medicine earning an intern's salary so I can relearn what I have forgotten.
Yes, a doctor's hours are worse (I have been working up to 120 hours per week) and the responsibility incomparably greater, but at the end of the day, a computer is an innanimate object. Helping people means far more and has far deeper rewards than the (short lived) euphoria of having designed a great program.
If you want to do any kind of computer work, do it in your (very scarce, I know) time as I am doing now.
And yes, as has been mentioned previously, the money and job security are also not to be forgotten.
Uh, 50% of people could be below the median starting salary. And the median is unlikely to be the average, unless you have a truly remarkable data set. (And no, you can't arbitrarily drop outliers.)
tasks(723) drafts(105) languages(484) examples(29106)
On the other hand, I'm in IT consulting, so I might be biased. I also really don't know that industry. Everything in this book may be wrong.
He's got a point... right now the industry is being outsourced left and right, and the job market is ridiculous. Most people (such as myself) are trying to get _OUT_ of the industry.
He isn't some college sophmore with nothing to his name. If he goes into a CS program, he doesn't get his MD revoked and he will probably start in a Master's program at least. Being a physician and in a tech will put him far above almost everybody else here on slashdot. This biocomputing or whatever with the supercomputers to solve biology problems, is one of the best fields to be in.
Forget programming, millions of people can do that -- but not many people can mix your two areas of expertise.
Berto
I was in your position 10 years ago, with an active Family Practice and a love of computers. I took advantage of a family move for my wife's career to change mine from medicine. I looked hard at CS, but ultimately decided that I'd be happier _using_ computers to do something, rather than supporting computers for those doing the research. So I ultimately ended up in Biochemisty/Biophysics researching protein crystal structures. It provides plenty of opportunity to work with computers in depth, while I still feel like I'm pushing back the limits of our knowledge. And the medical background has been quite valuable. It has been a fun move for me.
Good luck. Duke out.
In any industry you need to grow as a person and constantly increase your skills and knowledge to stay competitive. When I hear people whining about this outsourcing, all I can think of is the scores of developers I've seen in banks and other corporations that use their employers as resume mills and places to play with new tech.
While I am no longer able to bill $250/hr like I was during the dot-com days, I still have head hunters calling me up regularly, and have had no problem finding work.
To the original asker -- I know one woman who was a very successful doctor, and very successfully transitioned into software development, and now owns a company. Successful people are good at whatever they do. Get yourself a book and make a fake little project and start banging out some code. Attitude and personality transcend job type.
"Ain't I a stinka..." - Bugs
Nice a fellow Prarie home companion listener! Everyone makes a good point though. The world needs in general to restructure because there are too many tech workers an not enough demand for tech. I have a CS/EE BS degree and I hoped to do Unix Sys Admin or Embeded programming with that. Right now I am considering general electronics repairman because the market is so bleak. For the most obscure job expect a minimum of 100 applicants. My advice to all of you is stay in school or your current field/career. Don't quit your day job. Lastly the Tech fields and especially the computer field requires an encredible ammount of patience. It is extremely stressful in other ways that a physician might feel stress. In computers your patient doesn't always give you the feedback you need to fix them up. Your work is demanding and has health risks(carpel tunnel, back issues from sitting extended periods, ect). A doctor can feel stressed because you have a human life on your hands. A computer technician, programmer, sys admin feels the same stress because you have millions of company dollars on your hand. If you hoped to change careers because you didn't like the stress or hours of being a doctor your in for a rude awakening as a computer professional.
There is or can be built a machine that can simulate any physical object. -Church-Turing principle
Nonsense. That 40 year limit nonsense really ticks me off. I know an 82 year old woman who is better at computers than ANY young wippersnapper. She programs, scripts, and does linux, and she learned it in the '90s, all by herself. The age limit is really an HR ploy to keep older people off of the rolls because by the age of 40, most people actually have families, and the health and time expenses that go with them. It can be shown with any number of studies, that as long as the mind is stimulated, it continues to learn at a consistent rate until death.
Fast machines, powerfull AI, impulsive invention,... All I lack is a good espresso machine!
"all the children are above average"
Um, that's actually possible (almost). Now if all of the children are above the median, that'd be impressive.
>In many IT jobs you are old at 40, both because you can't keep up with all the new technology that comes along and because you are less creative at the problem solving that is at the core of many IT jobs.
That's totally bullshit. Some experience in a given field (in this case, medicine) FAR outweighs being sprightly. The "new technology" is never really THAT new, it's always some 1970s technology rehashed yet again. Personally, I'm one of those sprightly young programmers, but I wish my lab had more experienced programmers to show the young folks how it's done. I'm serious. Experience is MUCH more important than youth.
1) Ignore those who say there are no jobs in the market. This is simply not true.
2) Provide a unique service/slant towards what you do. The problem with many IT types is they lack of a systematic way of dealing with their network/PC gear. You would be amazed at the folks I have seen who run a few hundred machines literly by the seat of their pants. Nothing is written down, nothing is documented, the guy calls it 'job security' but it results in a real LOSS to his company at the bottom line, measured in downtime for the people who actually do work for the company.
Your age and experience in a 'real' field of profesional service will provide a great basis for a carreer in IT managment/Consulting.
3) Network! You know a lot of doctors. Docs are the BEST customers, because they are professionals. They will respect your ability, pay you, and stand back. You could concievably hit the ground running with your current circle of professional contacts, and never look back.
4) Laugh all the way to the bank and wonder how anyone could outsource a job that requires physical presence...
I respectfully disagree. You may be "old at 40" in many jobs relative to the age of new hires, but you are not at any disadvantage in terms of software development skills, creativity, experience, smarts, know-how, people skills, patience, etc.
As an old fart in my late 30s-early 40s I have watched young 18-year-old or 20-year-old hotshots from MIT come do a year or two of internship, or newly graduated 23-year-olds fresh from the compsci mills, and they are a marvel to behold; they talk fast, think fast, and type fast. However, they also make a big mess because they haven't learned how to be engineers yet, only coder/hackers. They are disorganized, they make huge mistakes in their designs, can't document for shit, they go down blind alleys... all the mistakes we also made as neophytes. Don't get me wrong--we love these young tykes and we know that when they're 35 they'll be awesome, but right now most of them can't program their way out of a paper bag. At the better companies, the management knows this as well. By contrast, I've noticed that older beginners tend to be more patient and humble and tend to "grow up" in the field a lot faster.
Regarding your contention that someone can be too old for anything, I would say that can't possibly be true. There are millions of people every year who discover their true calling and proceed to change careers in mid-life. This is what makes the U.S. such a great country; it's not the crooked politicians, the rigged elections, the oligarchical corporations, malls, racism, the self-centered lawsuit-happy masses, etc. It's the freedom and opportunity to go back to school and reinvent yourself, something which is next to impossible in most other places.
Ironically, I just had an interview today for a hospital volunteer position; I'm thinking of switching from software engineering into the healthcare field, maybe even medical school. The interviewer is a person who was once in theatre, now in hospital work, and is studying to become an ordained minister. Needless to say I got a very sympathetic hearing on my career aspirations.
One thing I've learned through all this is to never tell someone they can't achieve something. There are enough obstacles in the road so why create imaginary ones? If the O.P. wants to go into computers, more power to'em. Heck, if nothing else, they can moonlight in an E.R. once a month to pay the bills and still do what they love.
it's = "it is"; its = possessive. E.g., it's flapping its wings.
And who PAYS for all those little perks?
[SIG] Remember Mattel handheld games?