|
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...
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: There are developers writing code not for production?
I meant the production lines of our products : our products (mecatronics systems) are driven by software, and are assembled by production lines which are also drive by software. I meant the latter.
Kornfeld Eliyahu Peter wrote: Isn't that called QA?
No, it's deployment, and validation. You can emulate an assembly line up to a certain point, but sooner or later you need to test it on the real line.
~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.
|
|
|
|
|
I use to do nightshift, and very occassionally do them now, particularly around big turnaround or projects when we double up on managers due to criticality.
The software guys in the controls group also occassionaly do nightshifts as we work 24 hour operations, the projects run 24 hours, the commissioning must run 24hours.
Then you get the drilling schedules that dictate the well might be handed back to operations at 10pm and its all hands to the decks to get the thing on as quick as possible, e.g. a 5mbd well is a gross rvenue of 25,000 usd an hour, so timing is critical.
Then there is also the onshore process engineers and well guys who will provide the support to bringing on the wells and analysis the data to determine how to bring it on and what the data is telling us.
On the drilling side the geo guys are working 24 hours to make decisions on the reservoir and drilling targets as they cut through the various plays.
|
|
|
|
|
They can only afford a limited number of computers and need 'round the clock shifts to get the required through put?
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
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.
|
|
|
|
|
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  .
Software Zen: delete this;
|
|
|
|
|
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.
|
|
|
|
|
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! 
|
|
|
|
|
I only do right >> and left << shifts
Steve
_________________
I C(++) therefore I am
|
|
|
|
|
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
|
|
|
|
|
"The exaggerated publicity runs to the long bar where one may jump to in order to get far, far away... "(10)
Not too hard, but I like it.
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
Dalek Dave wrote: Not too hard, but I like it.
... as the actress said to the bishop
|
|
|
|
|
The exaggerated publicity HYPE
runs R
to the long bar SPACE
where one may jump to in order to get far, far away...
HYPERSPACE
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 – ∞)
|
|
|
|
|
Talking of things happening far, far away, Star Wars episodes 4, 5 and 6 have been on telly in the UK these past 3 Sundays and I made my 8 year old daughter watch them.
She guessed very, very, very early on in the 1st (4th) that Darth Vader was going to be Luke's father, much to my annoyance.
She enjoyed them though, and now wants to watch the first (last (middle?)) three.
She doesn't half ask a lot of questions though. I often think it would be much easier to have a stupid kid who just accepted everything.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
Ask long as the questions are the "short", "difficult", "important" ones: "How?", "Why?", "Where shall we have lunch?" that's what matters. If the questions start to be "isn't Beiber amazing?" and such like then disown or shoot her, quick!
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 – ∞)
|
|
|
|
|
Alice[^] from The Brady Bunch.
Another bit of my childhood has gone.
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
Greetings Lord David of Dalek,
My condolences on the passage of Ann B. Davis, but, you can take heart that your soul-brother, Chucky, is still going strong, and will, evidently, make another star-turn in the cinema in the near future: [^].
cheers, Bill
“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
|
|
|
|
|
Dalek Dave wrote:
Another bit of my childhood has gone.
Bit by bit, I remember her more from "The Bob Cummings Show".
R.I.P. Ann
If first you don't succeed, hide all evidence you ever tried!
|
|
|
|
|
Then you are really really old.
Like me.
|
|
|
|
|
GenJerDan wrote: Then you are really really old.
Like a fine wine! 
If first you don't succeed, hide all evidence you ever tried!
|
|
|
|
|
I've always avoided JavaScript programming like the plague as I find JavaScript to be a mess.
But I slowly realize that it's here to stay and that I need to get a clue about it.
The post below made me wonder not so much when to use which library, but rather when NOT to use a certain library.
I understand that JQuery is basically aimed at DOM manipulation, and Knockout is meant as a complement for doing MVVM binding, and AngularJS is trying to do both at the same time and is actually containing a subset of JQuery.
But there are plenty more JavaScript Libraries around, and I'm wondering not just when to use which but rather when NOT to use a certain library.
Discuss!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
