If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

/

Started by jina, 11 Apr 2011 04:50:20 PM

Previous topic - Next topic

jina

/
??

PRIT AMRIT


jina

#2
 >:(

PRIT AMRIT

quite straightforward, things are beyond your reach is 'Complex', within reach is 'Simple'  ;D

Lynn

Quote from: PRIT on 12 Apr 2011 09:31:00 PM
quite straightforward, things are beyond your reach is 'Complex', within reach is 'Simple'  ;D

Brilliant Prit!!

melee

Quote from: PRIT on 12 Apr 2011 09:31:00 PM
quite straightforward, things are beyond your reach is 'Complex', within reach is 'Simple'  ;D

In full agreement!

PRIT AMRIT

Lynn & Melee, thanks.. LOL

Well, it had happened with me once though. I was just new to Cognos then and had gone for an Interview. Was asked the same question that what are the kind of Complex reports you have designed so far. Then I started explaining few (multiple queries, cascading, master-detailed, etc etc...)and the interviewer is like it's not Complex. I am like, but it's Complex for me, could be damn easy for you as per your exp level....he just smiled..... funny it was  ;D




jina

#7
?

PRIT AMRIT

QuoteI was not expecting stupid answers from you (smart) people.

Smart people can only answer to smart questions ;D

cognostechie

Quote from: PRIT on 16 Apr 2011 12:15:10 PM
Smart people can only answer to smart questions ;D

Yup ! Absolutely correct  :)

Looks like the OP chickened out after posting some sentences so blanked out all his/her posts. I missed out on the fun  :(

Lynn

I'm not sure what caused bad feelings. The original question asked  people's opinions on what would be considered a complex report.

This is a common interview question. It is intended (in my opinion) to A) guage a candidate's ability to articulate their experiences in a clear and concise manner and B) allow the candidate to convey the various features and functions they've had an opportunity to work with. All of this is important to determine if the candidate is suited to the role.

Prit's answer was, therefore, perfect! It is an individual thing based on one's experience.

As someone who has been both interviewee and interviewer, I can say with sincerity that being open and honest about your experiences is significantly better than attempting to "study" stock answers and fool someone into believing you are more than what you are.

Here is an example and you can judge for yourself.....I asked two different candidates if they had used repeaters or repeater tables.

One candidate answered that he had, of course, used repeaters to prepare mailing labels recently for company XYX listed on his resume (a very large financial institution). The prospect of using Cognos to churn out mailing labels for a company this size struck me as odd since it would probably be a very large list no matter the type of recipient. I questioned further but he was unable to provide any detail, leaving me to assume he'd simply repeated (no pun intended) what he'd read in the user guide pretending it was his own actual experience.

The other candidate simply said that he never had a requirement to implement a report where repeaters made sense but he understood the concept (using the mailing label example from the user guide to explain) and further mentioned that he had seen an article in Support Link about using repeaters for creating a calendar of events (an article I had also seen).

I hope someone finds this to be a useful rather than a stupid answer. :)

cognostechie

Yes, I agree.

In fact, last year somebody asked me the same question (what kind of complicated reports have you made in RS) and I gave him a few examples but also added that it may or may not be considered complex by somebody else depending on the requirement and what is that person's skill level. I also said that now I don't find those reports as complicated because now I have done it a few times so it's relatively simple for me but at that time, it seemed complicated because I didn't have enough experience. He especially liked my last sentence on this ..'It all depends on what I don't know at that time which is what makes it complicated'.

I totally agree that one should not fake themselves to get the job but the sad part is that a major percentage of people still do that. I recently finished a project for a big insurance company who had started cognos implementation in 2009 end, hired a guy as a lead architect and fired him only in the beginning of this year and the manager told me that he didn't even know how to make one report all by himself. Result - Their FM Models and reports are mostly wrong and heavy maintenance which keeps giving wrong data in Production. I would also blame the management for this for going on with this for more than an year and realising so late..

jina

I 100% agreed to what cognostechie is writing.
But I am not that type person what you are thinking. I am a senior  software engineer(from USA).
I am also sick and tired of seeing all these people with fake degrees.
At the end we get all kind of  blame.
I am not a tough person. It hurts me when people think wrong way.
That's about it.

PRIT AMRIT

QuoteI am not a tough person. It hurts me when people think wrong way.

I apologies if my post did hurt you. Honestly, no offence intended though.

It's a forum and sometime we tend to pull each others leg, that doesn't mean we disrespect somebody. I believe that we all here in this forum to exchange our views and ideas about how we go with our day to day work and discuss about the issues/difficulties we do face.

Let's keep it simple and keep helping each other.

Thanks
Prit