|
BillWoodruff wrote: "I shall be released."
For me, Richard Manuels ghost will alway haunt that song. 
|
|
|
|
|
Interested in a game?[^]
Not affiliated to tombola bingo or any of its associates 
[Edit]
I have flabby Lincolnshire sausages instead of fingers, hence typos.
modified 2-Jun-14 5:22am.
|
|
|
|
|
Oh Dear God!
It is so me!
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
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 – ∞)
|
|
|
|
|
OriginalGriff wrote: night shifts
I do not even change to my kids at night...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
OriginalGriff wrote: Only thing I can think of is that he is being suckered into a Technical Support role
this.
|
|
|
|
|
OriginalGriff wrote: Large Company has offered him a development role as a "Process Specialist" but that the position might require he to work night shifts.
Not sure but it does sound like a BA role. He might be in the development team, just not a developer.
Signature construction in progress. Sorry for the inconvenience.
Damn you have the perfect signature - CBadger
|
|
|
|
|
Yes you are correct only support may required come at night shift.
But in my organization there is a segment where developers come in different shift because his full team is working from different geographical location. That may be the case here.
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
My previous employment required us to work shifts to support the key times of the business and that was because there was some technical support required.
If a problem arose that the first line support couldn't handle then it needed looking at by someone more technically capable very quickly at certain times of the day, typically 0600 to 0700 or 2000 to 2130. It often did require a knowledge of the code and particularly querying the database to see what was going on.
I loved working such shifts, and eventually became permanently lates, as from half 5 everyone else would bugger off and I was left on my own for four and a half hours in which I could get on with what I wanted (I played a lot of Transport Tycoon). Support calls were typically zero to three a night and eventually I did take on first line support as well (for an extra £15 a night) as 90% of calls at that time would require me and those that didn't were very quickly dealt with.
I have also heard of developers working shifts to fit in with the working times of offshore development for the same company / product.
[Edit 1] I should say that it was a small development team, and there were only 4 of us really trusted to do this role, with another one or two who could be left in charge if we really had to.
[Edit 2] I once did the early shift, from 0600, then the lad who was supposed to be doing the late shift phoned to say his dad had died, everyone else was away on a course so I stayed for the late shift too, til 2200. A week later I was late for a normal 0900 start and given a large bollocking, not a mention was made of the previous week. This was one of the things that contributed to me wanting to leave.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
chriselst wrote: A week later I was late for a normal 0900 start and given a large bollocking, not a mention was made of the previous week.
No good deed goes unpunished. 
Once you lose your pride the rest is easy.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am.
JimmyRopes
|
|
|
|
|
Your friend is lucky to have you flying at his wing to warn him ! It's a little known factoid that QA actually is derived from the Latin root "quisque abomini:" "every horror."
I discount the theory of some that it derives from "quadruplor assiduo," or, "assiduous informer/spy," not to mention theories that the "a" stands for a part of human anatomy, and the "q" for a word describing an unspeakably bestial act.
“I'm an artist: it's self evident that word implies looking for something all the time without ever finding it in full. It is the opposite of saying : ‘I know all about it. I've already found it.’
As far as I'm concerned, the word means: ‘I am looking. I am hunting for it. I am deeply involved.’” Vincent Van Gogh
|
|
|
|
|
The developers of the code for the production lines work night shifts, partly for support, partly because they have to test their changes on the production at some point, and make trial and error, and the production does not wait until the next morning.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
Rage wrote: developers of the code for the production lines
There are developers writing code not for production?
Rage wrote: test their changes on the production
Isn't that called QA?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
The real world isn't nicely compartmentalised.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
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 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)
|
|
|
|
|
Ah, web pages.
So, not the real world then.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
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... 
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! 
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)
|
|
|
|
|
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...
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)
|
|
|
|
|
OriginalGriff wrote: before it's handed to QA
QA = the users...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
