|
Thanks a lot. I was happy never to have seen that video.
The girl had no idea what she was doing.
|
|
|
|
|
Only have managed to destroy a couple of thousand(USD) in a day. I use to work in destructive testing and I miss judged the failure location. Thus losing instrumentation.
I now can cause endless grief as a DBA but usually I do not cost the company (too much) money.
|
|
|
|
|
I destroyed one of only three existing protoypes of a new model of printer, by plugging the mains connector in one pin out, and putting 240VAC onto it's earth line.
While building it, the day it and both it's pals were due to be driven out to a 10 day trade show in Germany by the company owner...
Direct costs:
Print head £1000.
Dead as a dodo.
PCB: around £4000 as there were only three in existance (and one of them was rather flaky since it was the first build and had the most changes). All SMT, all built by hand, including a 0.4mm lead pitch 304 pin QFP processor of which 4 had been specially flown over from Japan for the build...
Very, very dead. Over 50% of the tracks vaporised...
Indirect costs: Unknown. Only two machines on a stand designed for three? Oops. 
In my defence, I immediately changed the company standard PCB mains connector so it couldn't happen again, and I had been working every hour there was for 5 months to get the hardware and software from "fag-packet" sketch to hardware.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: SMT, all built by hand, including a 0.4mm lead pitch 304 pin QFP
I pity the person that had to handle this migrane inducing reason to die job. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
|
|
|
|
|
It took her a while - about an hour of mental prep, and then about five minutes per device - most of which was visual checking under a strong glass.
Oh and she didn't drink the night before!
(She's sitting next to me as I as I post this)
The production models went through the SMT cooker, and as I had a higher failure rate until they got the temps / times right.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Good technicians are indeed a godsend! Even with nice optics, I still get a headache looking at the soldering job/part placement on prototypes.
OriginalGriff wrote: higher failure until they got the temps / times right
Ah, the fun of a new product. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
|
|
|
|
|
OriginalGriff wrote: (She's sitting next to me as I as I post this)
You met your Missus at work?
|
|
|
|
|
No, I met her at the pub - she was going out with a friend of mine, until he decided to start smacking her around.
We started going out, and when the company I worked for needed another PCB assembler I suggested her. She became the prototype builder (because she was far and away the best at it) and was responsible for moving the company from leaded to unleaded solder before the EU directives came into force in 2001, and then into SMT from PTH.
We kept it professional at work, and customers never even knew unless they saw us out of work.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I've bricked some SBCs (not is the same day, though).
THESE PEOPLE REALLY BOTHER ME!! How can they know what you should do without knowing what you want done?!?!
-- C++ FQA Lite
|
|
|
|
|
Most I can recall was accidently shutting down a production database and having all the call center staff idle for twenty minutes or so -- boss estimated it at 3000 USD or so.
It's his own fault... he asked me to write a script that would allow the operators to easily stop and start the database for backups. The script worked perfectly of course.
|
|
|
|
|
Direct mistake was an unchecked auto generated document with a spelling mistake - recieve rather than receive - that went through a production run. Around 20,000 letters to be converted to fire lighters.
Indirect would be a bug feature in a piece of software that brought a retail banks card system down on Christmas Eve. In my defence, my part was providing balances for authorisation online and the card system should have switched to offline limits rather than nacking everything.
|
|
|
|
|
Yes, I know the question has been asked before, but things change and so does opinions.
I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time.
...
And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. 
<edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
|
|
|
|
|
|
|
|
I'm seeing a pattern here.
Are you at a big company?
|
|
|
|
|
Been at very large and now at reasonably small. Have used many different systems over the years but have found TFS to best fit the need.
What really helps has been getting a TFS consultant in to make sure the system is set up so as to best serve our needs.
|
|
|
|
|
Fourthed.
I use it at work (large company, enterprise software development) and for myself (1 person shop).
/ravi
|
|
|
|
|
Something that comes after 4th (I'm wearing mittens so counting function in maintenance mode)
cheers
Chris Maunder
|
|
|
|
|
Well, for my private installation (just me and a handful of machines) I'm still using VSS with VS2008 and it's been fine but, yeah, in an environment with multiple developers I'd definitely go with TFS.
|
|
|
|
|
How many developers ?
What target technology ?
How many location (including writing tickets, reading tickets, development, testing, etc...) ?
~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.
|
|
|
|
|
We're a very small shop with an IT department that just shrunk to below ten people, but the number of people that should be able to write tickets counts in thousands.
We're exclusively doing Visual Studio for the foreseeable future.
|
|
|
|
|
Jörgen Andersson wrote: We're exclusively doing Visual Studio for the foreseeable future.
TFS (sixthed?)
|
|
|
|
|
We use JIRA and SubVersion; and will be soon using the Crucible (codereview) and FishEye (code tracking) JIRA plugins.
I'd rather be phishing!
|
|
|
|
|
Are you happy with Jira? Any specific gotchas?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
