Ask Slashdot: Getting My Wife Back Into Programming After Long Maternity Leave?
An anonymous reader writes: My wife has been on a maternity leave for three years, now. She is starting to think about refreshing her coding skills and looking for a job. Before, she worked as a Java developer for around two years doing mostly Java Enterprise stuff. However, she is not very eager to go back to coding. I think she has the right mental skills to be a developer, but she is just not very passionate about coding or IT in general. On the other hand, it's relatively easier to find a job in IT than starting a new career.
We live in Spain, and with the current economic situation, the market for software developers is not great — but it's definitely better than other jobs. I there anything else she might do, ideally Java (but could be anything IT related) that would be easier and more fun than the typical Java Enterprise stuff, while also giving her a good change to find a decent job? (I'm a Java developer myself with many years of experience but mostly doing boring Java Enterprise stuff.)
We live in Spain, and with the current economic situation, the market for software developers is not great — but it's definitely better than other jobs. I there anything else she might do, ideally Java (but could be anything IT related) that would be easier and more fun than the typical Java Enterprise stuff, while also giving her a good change to find a decent job? (I'm a Java developer myself with many years of experience but mostly doing boring Java Enterprise stuff.)
My wife was out of the programming workforce for about twenty years, and worried that her FORTRAN skills were no longer needed :-)
I encouraged her to take some Java classes, she liked it a lot, found an interesting job and several years later is loving it.
The thing is, do the research to find an *interesting* job -- yeah, it may be just "Java Enterprise stuff", but if it's an interesting project, and something you believe in, with good people, it's worth doing. My wife's team is a crazy bunch, and she enjoys their interactions (and telling me the wild stories) a lot.
She's been able to learn a lot of useful side technologies (XSLT, Databases, basic web stuff, etc.) so she'll be able to find a new job if the rumors of them moving the project she's on several hundred miles away pan out.
Anyway, with you working, she doesn't have to settle for the "first available" job, look around a lot, interview a bunch (if nothing else, to hone interviewing skills).
Good luck to you both!
+1
Not to be sexist, but most women prefer jobs that include more interaction with people and less time spent in solo problem solving, so it's not terribly surprising that she does't love coding. This isn't to say there aren't women who really like coding, or even introverted women who find working with people all day to be unpleasant. There are all kinds... but on average my observation is that women prefer more human interaction.
So, assuming that your wife falls into that category, there are lots of roles in and around software development that are more people-focused. Project management requires an additional set of skills, both people skills and management skills, but it's eminently learnable, and having a technical background is very valuable -- as long as it doesn't cause her to second-guess what the developers are telling her (always a risk with PMs, and even more with those whose technical background is shallower than they think it is. There's a tendency to assume that everything they don't know how to do is easy.)
Business Analyst is another good one. It, again, requires some additional skills she probably doesn't have but can learn. Industry knowledge tends to be important, but most companies are okay with analysts learning that context on the job. She also needs to learn how to gather and document requirements. A technical background is useful there because good requirements need quite a bit more precision than most non-technical people are used to. There's also a risk; formerly-technical BAs have a tendency to overspecify. An important skill for this role which isn't so easy to learn is writing. Good BAs are excellent writers, able to concisely and accurately boil complex issues down to simple statements.
Another option that might be excellent if she can swing it is Systems or Application Architect. Companies generally want experienced, senior developers to move into these roles, but smart but less-experienced people can do it as well. Architects take the business requirements and convert them into high-level technical plans/architectures. Architects tend to spend less time interacting with people than PMs or BAs, but still quite a bit since they provide the primary interface between the technical and business teams. Architects need to have good technical skills and good "taste", meaning a good feel for what sorts of structures are easy to build, easy to maintain and flexible, and for how to intelligently trade those issues off. They also need to be good at translating technical issues into language the business people can understand. Honestly I expect that your wife probably doesn't have the depth of experience needed to make a good architect, but I thought I'd throw it out.
Another that might be good if she's a good writer and enjoys writing is technical writing. Good tech writers have greater need for writing skill than they do technical skill, but the latter is very valuable because it enables them to more quickly and accurately understand the information that needs to be documented.
In smaller companies a lot of these roles get mixed and combined with other business roles, so another good option is to look for a position that isn't necessarily directly related to software development, but could benefit from having a deeply IT-literate person.
Finally, the option that I've long thought I'd take if I ever got tired of writing code is the law. It's a lot of additional training, but I think there is a deep and growing need for attorneys who understand technology. This is especially true in the areas of patent and copyright law, but I think it applies in many areas. Of course, the law may not have any attraction whatsoever for your wife.
Whatever, I'd really encourage her to take the time to figure out what she wants to do, and do that, rather than settling for something she doesn't really like. We so much of our lives working that it's really a waste to spend it doing something we don't like.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
I can't speak for either of those professions, but I stayed home for about 6months with my two toddlers (honestly easier than one because they play together), and trust me, it isn't easy. If you actually parent/clean/cook and don't just screw around watching tv and facebooking all day it is pretty constant physical and mental labor. By the end of my run, I was ready to get back to programming. On top of that it really is a thankless job with criticism when you are having a bad day. At least when you are having a bad day programming, you just open up slashdot and slack for a few hours. Do that when you are at home and the house is trashed. Then it becomes mentally debilitating because it's a job that is never done and if you are consistently doing it 24/7 it all goes to hell.
In regards to coal miner or roofer, again I can't speak to those professions, I can say as a person who worked in construction for 5 years during school, I'd rather be doing that then chasing kids around (if only it was just that).
Oh and nap time is the time to get shit done, it aint rest time. There are no breaks. And when you are the SAHP your the primary care giver and the other person disconnects so instead of working 40hours a week like your spouse you work essentially 7 16hour days.
WTF Slashdot, why do I have to login 50 times to post?
So that nest egg... is it invested into stocks that require workers younger than you? Is it invested into government bonds which require taxpayers younger than you? Is it invested into banks which require people taking and paying loans who are younger than you? Are you going to spend them at stores staffed by people younger than you, with things made by people younger than you, and delivered by people younger than you? Without young'uns being born at a pretty consistent rate, you'd see some piss poor returns on your investment.
Watch for Penguins, they eat Apples and throw rocks at Windows.