Anyone here do "night shifts"?
-
I take it you've never been a developer in a very small team in a totally none tech related business then, or been the only developer in a company, or been a developer who also has responsibility for servers and networking and email and anything to do with a plug really. You know, the real world.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
Wrong. I'm leading a 5 person team (4 developer + 1 system guy). We run a project that has over 500 web pages grouped into 4 personal portals. The application installed on over 2000 servers and all of them is our responsibility. However, running test late night on the production servers by a team member is something that never happened. Also production test of the code by the developer is something that never happened (and will not as long as I'm here). And the reason is simple - you can not trust a developer to test his own code, he will not do it right...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Wrong. I'm leading a 5 person team (4 developer + 1 system guy). We run a project that has over 500 web pages grouped into 4 personal portals. The application installed on over 2000 servers and all of them is our responsibility. However, running test late night on the production servers by a team member is something that never happened. Also production test of the code by the developer is something that never happened (and will not as long as I'm here). And the reason is simple - you can not trust a developer to test his own code, he will not do it right...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I'm working in the real word over 15 years and never asked to do QAs job - it is even wrong to let developer test his own code!
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
I test my code all the time, and always have. Developers who don't test their code are just guessing that it works. And if you assume it does, you can construct an enormous software edifice before it's handed to QA who find it doesn't even walk, let alone run! :laugh: Not formal acceptance testing, no - but even limited functional testing to ensure compliance with the specification needs access to the data or hardware it will interface to.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt -
I've had an odd email from an associate, in which he says that a Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts. Now, I live a sheltered life, but I've never heard of developers working shifts, (heck, getting us to work at regular hours is hard enough) much less night shifts - in fact I can't think of any "thinking", "creative" position that does shift work at all! Is this normal now, out in the Big Wide World? Only thing I can think of is that he is being suckered into a Technical Support role, not development, in the full and certain knowledge that once he joins that Legion Of The Damned (even temporarily) the only ways out are Suicide and Mass Murder...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I did night shifts for a while. The MO was I was embedded on a client site and they were going through branch migration. Every week 2-3 branches moved over to the new system. All the live data loading was done at night to alleviate load on the system during working hours and I was supporting the bank in case "Fan In Excresia". I started work at midnight so my routine was to get up at around 8, go out to dinner and then go onto work. I, of course, never drank when I had to go to work. Well hardly ever. I finished at 8 in the morning when the rest of the team got in; the namby pamby day shift. Then I'd go to a nice little tavern near home that served a decent breakfast and I'd have a half carafe of wine afterwards. Maybe a second one. Bed by noon. While I was in work I provided around 13 seconds of support each night. Crucially we were also developing an interface into the cash machines; not ATM's but safes that under the tellers desk and dispensed notes. The bank had only one spare machine, they were frogging expensive, and it was in the training room. So each evening I'd plug the cash box into my faithful lappie and hack away carefully work through the spec. During that period, I was being billed for [0] on-site support, [1] out of hours migration support and [2] developing the cash machine interface. Triple billing and thank-you very much big bonus.
-
I test my code all the time, and always have. Developers who don't test their code are just guessing that it works. And if you assume it does, you can construct an enormous software edifice before it's handed to QA who find it doesn't even walk, let alone run! :laugh: Not formal acceptance testing, no - but even limited functional testing to ensure compliance with the specification needs access to the data or hardware it will interface to.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Test his own code as a QA test I mean. Of course you run it to test sanity, but never for production test. That's a different beast...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
"It never ceases to amaze me that a spacecraft launched in 1977 can be fixed remotely from Earth." ― Brian Cox
-
Test his own code as a QA test I mean. Of course you run it to test sanity, but never for production test. That's a different beast...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Yes - but if you are supposed to be driving production equipment, then you need to run your code on production hardware - preferably when it isn't in use and it doesn't matter if it fails in spectacular fashion. As it will, the first couple of times... :laugh:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt -
Yes - but if you are supposed to be driving production equipment, then you need to run your code on production hardware - preferably when it isn't in use and it doesn't matter if it fails in spectacular fashion. As it will, the first couple of times... :laugh:
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I have no experience with hardware - so i can't really tell what I would do there. All my opinions about software-for-software development...(And that fails also a lot ;) )
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Wrong. I'm leading a 5 person team (4 developer + 1 system guy). We run a project that has over 500 web pages grouped into 4 personal portals. The application installed on over 2000 servers and all of them is our responsibility. However, running test late night on the production servers by a team member is something that never happened. Also production test of the code by the developer is something that never happened (and will not as long as I'm here). And the reason is simple - you can not trust a developer to test his own code, he will not do it right...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I test my code all the time, and always have. Developers who don't test their code are just guessing that it works. And if you assume it does, you can construct an enormous software edifice before it's handed to QA who find it doesn't even walk, let alone run! :laugh: Not formal acceptance testing, no - but even limited functional testing to ensure compliance with the specification needs access to the data or hardware it will interface to.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
OriginalGriff wrote:
before it's handed to QA
QA = the users...
-
I think you missed something here it was production LINE, possibly manufacturing. I have worked night shift in such environments where you can get at the machines.
Never underestimate the power of human stupidity RAH
Yeah. I got that from OG too... :sigh:
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
I've had an odd email from an associate, in which he says that a Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts. Now, I live a sheltered life, but I've never heard of developers working shifts, (heck, getting us to work at regular hours is hard enough) much less night shifts - in fact I can't think of any "thinking", "creative" position that does shift work at all! Is this normal now, out in the Big Wide World? Only thing I can think of is that he is being suckered into a Technical Support role, not development, in the full and certain knowledge that once he joins that Legion Of The Damned (even temporarily) the only ways out are Suicide and Mass Murder...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Folks in my group do occasionally to do testing on our prototype machine. Some of this happens on second shift, because: In their Infinite Wisdom, the Powers That Be dictated that There Shall Be Only A Single Prototype, and You Sniveling Engineers Can All Share. And they said I was crazy for wanting to do user interfaces. No travel to customers, no night shift :-D.
Software Zen:
delete this; -
I've had an odd email from an associate, in which he says that a Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts. Now, I live a sheltered life, but I've never heard of developers working shifts, (heck, getting us to work at regular hours is hard enough) much less night shifts - in fact I can't think of any "thinking", "creative" position that does shift work at all! Is this normal now, out in the Big Wide World? Only thing I can think of is that he is being suckered into a Technical Support role, not development, in the full and certain knowledge that once he joins that Legion Of The Damned (even temporarily) the only ways out are Suicide and Mass Murder...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I lobbied for, and got, my own special shift when I worked in germany. 1400 - 2200 That gave me 4 hours to interact with the people who didn't understand anything, and 4 hours to actually get some work done. It was bliss.
-
I've had an odd email from an associate, in which he says that a Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts. Now, I live a sheltered life, but I've never heard of developers working shifts, (heck, getting us to work at regular hours is hard enough) much less night shifts - in fact I can't think of any "thinking", "creative" position that does shift work at all! Is this normal now, out in the Big Wide World? Only thing I can think of is that he is being suckered into a Technical Support role, not development, in the full and certain knowledge that once he joins that Legion Of The Damned (even temporarily) the only ways out are Suicide and Mass Murder...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
The Indian company to which this potential employer has outsourced decided to work during daytime in India. So, necessarily this guy will have to work the night shift to be in sync with them! ;P
-
I've had an odd email from an associate, in which he says that a Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts. Now, I live a sheltered life, but I've never heard of developers working shifts, (heck, getting us to work at regular hours is hard enough) much less night shifts - in fact I can't think of any "thinking", "creative" position that does shift work at all! Is this normal now, out in the Big Wide World? Only thing I can think of is that he is being suckered into a Technical Support role, not development, in the full and certain knowledge that once he joins that Legion Of The Damned (even temporarily) the only ways out are Suicide and Mass Murder...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I only do right >> and left << shifts ;)
Steve _________________ I C(++) therefore I am
-
I've had an odd email from an associate, in which he says that a Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts. Now, I live a sheltered life, but I've never heard of developers working shifts, (heck, getting us to work at regular hours is hard enough) much less night shifts - in fact I can't think of any "thinking", "creative" position that does shift work at all! Is this normal now, out in the Big Wide World? Only thing I can think of is that he is being suckered into a Technical Support role, not development, in the full and certain knowledge that once he joins that Legion Of The Damned (even temporarily) the only ways out are Suicide and Mass Murder...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I guess Chris is doing Night Shifts pretty often. Would guess they use the term as in "Work more if there is more work to do."
I will never again mention that Dalek Dave was the poster of the One Millionth Lounge Post, nor that it was complete drivel.
The console is a black place [taken from Q&A]
How to ask a question
