183 reputation
17
bio website burnedoutprogrammer.blogspot.…
location Melbourne, Australia
age 35
visits member for 2 years, 7 months
seen Apr 11 '12 at 3:17

Learn to sanitize your database inputs.


Nov
10
comment Resume and job seeking advice - career change from Development to Testing
"You say that you are a former developer. What are you doing now?": I burned out early this year and essentially took a self-funded mental health career break. Initially I thought it was just burnout related to the particular stresses of that given job, but on my time off I realised that it was more about programming itself, and not being quite cut out of it. Obviously, this sounds like a pretty dysfunctional breakdown (although it wasn't really), so I'll have to be careful how I sell it.
Nov
10
comment Resume and job seeking advice - career change from Development to Testing
BTW, in Australia it's basically standard to have a 3 month probationary period in new jobs where it's essentially entirely "at will". But yes, after this it's fairly hard (by US standards) to get rid of someone, unless they're very blatantly not working out.
Nov
10
comment Resume and job seeking advice - career change from Development to Testing
+1. For the record, I also suffered a massive burnout as a developer. Essentially took a career break when it got too much earlier this year. But I'm trying to package this in a way that doesn't sound like a totally dysfunctional breakdown (it wasn't really, but it's hard to describe without sounding it). :)
Sep
12
comment Going from Development into QA?
+1 Interesting. Yes, I'm quite aware of the politics of having to release less-than-perfect, etc. I found being on the Development end of this more stressful, because trying to squeeze in last minute changes/fixes often breaks other things, and I hated looking bad because of that. When I was on the testing side of it I didn't find it as bad - I simply documented oustanding issues and noted "don't say I didn't warn you that this defect is still in the release.". But I can imagine in certain environments this would be stressful too.
Sep
11
comment Going from Development into QA?
@user246 re: your edit + links: Thanks. Those were very insightful. Mostly in a good way (as in confirmed that I'm far more cut out for testing than for development).
Sep
11
comment How do you prepare yourself for a testing position?
+1 Good answer. As someone currently considering moving from development to testing/QA, this really struck a chord: "be curious & ask questions, but remember it isn't our job to fix the problem. We can provide suggestions and ideas but ultimately the decision on what and how is oustide our responsibilities." - this is pretty much what's driving out of development and into testing. My mindset has always been better for testing than development this way.
Sep
11
comment Going from Development into QA?
I should clarify: I love tracking down bugs, I just don't like being the one who has to fix it, or being the one who risks breaking something else with those changes. There's just something about being the "direct doer" of something instead of a pure analyser that really doesn't work for me. It's hard to explain, but very real. And yes, re: user246's question, what's the actual difference between Testing and QA? It's always been interchangeable in organisations I've worked with.
Sep
9
comment Going from Development into QA?
+1 Thanks. Good points. :) I was going to use the term "seeing the forest for the trees" too. I think all my problems with development have this same root, which is why it was hard to make separate points without referring to "meta knowledge work" constantly. I really can't explain why I have a problem with details when I'm directly involved in creation/changes of the knowledge capital, but not when I'm one step removed. But this is the key to the whole thing. :)
Sep
9
comment Going from Development into QA?
+1 Thanks. See my comment on Joe Strazzere's post re: responsibility. As far as prestige and pay goes, I'm not at all phased there.
Sep
9
comment Going from Development into QA?
+1 Thanks. I should clarify: taking responsibility is only really an issue for me in the context of directly working on something and creating it (making direct changes to the concrete object of the work) myself. It doesn't come up when the work consists of analyzing something from a step back. I suppose part of this is confidence: I'm just much better at stepping back and seeing details than seeing them when I'm buried in them - and being good at something equals being more confident to take charge of it. By no means is this a totally generalized issue of not wanting responsibility.
Sep
9
comment Going from Development into QA?
+1 Thanks. I'm definitely not phased about the salary and prestige aspects, but I can see what you mean about the taking responsibility issue. I should note though: this one is massively magnified by being the actual front-line creator of something (rather than an analyser who is a step removed).