Christian Berg wrote:

user12240205 wrote:


If you have hands on experience then according to you, certification is not necessary since you can answer any question asked in an interview, right?


(1.) Are you worried about an interview? Being worried about being able to actually do the job one's getting paid for and not letting down a client who depends on you seems to be more important but that may be a personal attitude.



user12240205 wrote:

Then what is the point in these certifications, other than somebody like me letting prospective employees know that I have enough knowledge to take over and continue?


(2.) Certification without knowledge, comprehension and understanding is nothing. The last three without certification are just fine though. Think about it - would you prefer brain surgery from a doctor with 500 successful operations and 1 diploma or one from a doctor with 50 diplomas and zero successful operations?


user12240205 wrote:


Like, if they have an OBI implementation, I will need to only learn their business scenarios. Since I have the certification, I will not need to know any OBI technical stuff. Doesn't getting certified show this?
(3.) "I will not need to know any OBI tchnical stuff"...errr how did you get to that conclusion? If one doesn't "know any OBI technical stuff" then why should that person be on an OBI project?

(1.) I am worried about both. Since I have been doing development in other Oracle technologies I can easily switch from one to another. Here I am more worried about the interview. Once I get in, since I have the OBIEE technical knowledge due to doing the certification, I can give 100% attention and get to know their business problems. Since I now have paid job (with a certification also), that can give enormous boost to my self confidence and hence help me in learning the ropes quite quickly.

(2.) You can't compare brain surgeons with software engineers. One is a very high-risk profession while the other is not. Nobody is going to die because you made an error in a Business Information System like a financial reporting system or ERP. At most the customers and end users will get delayed in doing their activities and in the worst case loose some money due to downtime.

(3.) What I meant was, since I learn the OBI technical stuff while doing the certification, once I pass the interview and join the company, I will only need to concentrate on the business problem to which OBI was applied. I might have to learn technical stuff which is learnt only through experience, but this can be done with effort since now I am employed and hence the employment gives me great confidence.

Gianni Ceresa wrote:


Daniel Willis wrote:

So the next question is.. has anyone got a study guide for Christian's interview catalog?

The only working solution I had till now was to get him drunk before the interview 
But in general I will say that you can do it if you really use the tool for what it is supposed to do (so forget DDR and spend time modelling things in the RPD) ....

user12240205 :

(2.) You can't compare brain surgeons with software engineers. One is a very high-risk profession while the other is not. Nobody is going to die because you made an error in a Business Information System like a financial reporting system or ERP. At most the customers and end users will get delayed in doing their activities and in the worst case loose some money due to downtime.

Well ... that's just a matter of point of view ...
You make errors in your model and so the financial reporting is wrong, the company use these numbers to publish their yearly financial results (so wrong numbers). It will not be solved with just a delay and some money but you being fired and if you are lucky it end there ... If not lucky the company get a huge fine from financial markets control authorities, they must do a full audit, republish numbers and in the end it will costs to the company few millions ...
Sure you are not death like the guy with brain surgery, but you are financially and professionally death ...

Seriously?? Have your ever heard of a software developer getting fired due to a software bug or design flaw??? I have not.

Here is an article on the subject:http://www.datamation.com/columns/smit/article.php/3839981/Why-Developers-Get-Fired.htm

which gives these very valid logical reasons:

(a.) If your job consistently isn’t getting done, then you will eventually be toast.

(b.)  If your deliverables are always late

As you can see, when a new employee is taken in, normally he is given a 6 months probation period. So, he is evaluated at the end and only made permanent.

Unless you have shown gross incompetence over a long period of time, I don't see how anybody can get fired just because a bug or design flaw?

Not that I am saying it's OK to design bad software or have bugs in your code, but that is just part and parcel of the software field, isn't it???

Do you think people get fired when car companies recall millions of faulty vehicles? I don't think so.

Do you think the British government prosecuted the software engineers responsible for the 1994 Chinook helicopter crash which killed 29 people?

https://en.wikipedia.org/wiki/1994_Scotland_RAF_Chinook_crash

Do you think they went after the software engineers responsible for the ARIANE 5 rocket crash of 1996??? They did not. The Ariane 5 had cost nearly $8 billion to develop, and was carrying a $500 million satellite payload when it exploded

The report (ARIANE 5 Failure - Full Report ) clear state that " the failure was due to a systematic software design error".