Candidate : pops in, pulls a chair,sits down and makes himself agreeable for the interview
Interviewer : Well, Mr.X ,I See you have a good degree etc etc...Have you come across this book, may be read it , it's called 'Code Complete' by Steve Mc Connell ?
Candidate : Err,.Eh, not sure,yes may be.
Interviewer : Thank You! , eloquently points his finger at the door.
Rob Miles, our guru and mentor speaks thus when asked something like 'how do you price software for good revenue keeping the risk triangle in mind' ?
Rob Miles: Software should be priced in such a way that by the end of the project, the stakeholders go home happy and you're left with money just enough to buy a speed boat!!. Now, that's Job Well Done!!
An XYZ company's marketing spokesperson was demonstrating the dynamics of his company's new 'cool speech recognition software' to an audience;
you are about to witness a revolutionary software product now he said, and he clapped his hands;
Welcome it said, 'what can i do for you' ?
the man ordered; 'start' 'program1' 'type' 'email' etc etc..
the 'smart' software obediently and elegantly executed every order of his, The audience viewed the demo in serenity.. suddenly,
someone at the back shouted:
'Run' 'Format' 'C Colon' 'Yes'
Hi,
I'm reading this book by Karl E.Wiegers called Software Requirements, published by MS press. The most intriguing part of the otherwise boring book are the interactions between employees before every chapter..
Often, 'small deviations' during requirement analysis leads to doom during development/deployment phase. Also, not often it's realized that those 'small deviations' during requirements engineering was the cause., the actual 'creep' which lead to doom. This book throws light onto those areas and helps you avoid getting doomed early on, even before you start negotiating a software deal with a client..
