Home > Archive > microsoft.public.cert.exam.mcsd > September 2003 > Failed 70-300 Again !!!!





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Failed 70-300 Again !!!!
tommylee

2003-07-17, 12:23 pm


Dawn !!! I hate this test... this is my last test to be MCSD.NET but I
failed TWICE....I passed the other tests on the first attempt. I don't
know if I continue to pursue this or just give up and be a MCAD ? Any
one in similar situation ?
The thing is I don't know what I did wrong. I thought I should get
correctly above 90% of the questions. So if I get the same test, I
probably will fail again.

--
Posted via http://dbforums.com
emg

2003-07-18, 9:24 am

Have you tried Transcender? I haven't attempted this particular exam but I
have used them for other exams. They really help focus your studies and
provide explanations of why some answers are right and some are wrong. I
know it costs as much as taking the exam, but if you're taking the exam
multiple times with no clear idea of why you're not passing, you need to try
another tack.


"tommylee" <member32008@dbforums.com> wrote in message
news:3122006.1058453253@dbforums.com...
>
> Dawn !!! I hate this test... this is my last test to be MCSD.NET but I
> failed TWICE....I passed the other tests on the first attempt. I don't
> know if I continue to pursue this or just give up and be a MCAD ? Any
> one in similar situation ?
> The thing is I don't know what I did wrong. I thought I should get
> correctly above 90% of the questions. So if I get the same test, I
> probably will fail again.
>
> --
> Posted via http://dbforums.com



tommylee

2003-07-18, 1:24 pm


Thanks, Emg.
I will try that... I think I failed because I don't have the experience
as an architect !? I have been a developer...

--
Posted via http://dbforums.com
John S

2003-07-19, 7:23 am

> I think I failed because I don't have the experience
> as an architect !? I have been a developer...


Should be considered the same title.

Software Engineer, Software Practitioner, Analyst Programmer, Software
Developer, Software Architect are all the same.

Software development is not just about slapping a few controls on vb form or
writing a bit of C# code. So maybe you should just give up or become
professionally competent in what you do for a living.

"tommylee" <member32008@dbforums.com> wrote in message
news:3126931.1058544056@dbforums.com...
>
> Thanks, Emg.
> I will try that... I think I failed because I don't have the experience
> as an architect !? I have been a developer...
>
> --
> Posted via http://dbforums.com



Jamie

2003-07-21, 10:24 am

you are nearly correct John.....

A Software Architect is a higher level position than a mere(!)
programmer.

not everyone that gets employed by a company to cut code will be
equal. Skills come with experience, as do pay rises!

At my company (a small software house), we have 3 Software Architects
who are the gurus of the company, we then have maybe 7 senior level
Software Engineers/Developer etc (like me), then about 3 lower level
Developers.

The lower level developers wouldnt have a clue as to how fit complex
network/internet enabling technologies like Remoting or Web Services,
how to design a database or why Stored Procedures are a good idea, or
why Triggers can confuse people (like them!)

The Software Architects are the ones that plan how the system is going
to fit together on the larger "whole" scale. The senior developers are
somewhere in between.

:-)





"John S" <John@notreallyhere.tv> wrote in message news:<#nnUcceTDHA.1912@TK2MSFTNGP12.phx.gbl>...
> > I think I failed because I don't have the experience
> > as an architect !? I have been a developer...

>
> Should be considered the same title.
>
> Software Engineer, Software Practitioner, Analyst Programmer, Software
> Developer, Software Architect are all the same.
>
> Software development is not just about slapping a few controls on vb form or
> writing a bit of C# code. So maybe you should just give up or become
> professionally competent in what you do for a living.
>
> "tommylee" <member32008@dbforums.com> wrote in message
> news:3126931.1058544056@dbforums.com...
> >
> > Thanks, Emg.
> > I will try that... I think I failed because I don't have the experience
> > as an architect !? I have been a developer...
> >
> > --
> > Posted via http://dbforums.com

John S

2003-07-21, 12:23 pm

No I am correct. They are just titles which mean the same thing. What your
company describes as a 'Software Architect' is what my company describes as
a senior (or principle) software engineer, another company my title that
role as senior analysis programmer or designer. Naturally there are
different grades which reflect the individual's experience and
responsibilities, i.e. principle, senior, junior or just plan grunt.

BTW, I don't know of any company that employs people to 'just cut code' -
case tools do that.

"Jamie" <j.mo@lycos.co.uk> wrote in message
news:ce580daa.0307210557.3c46862@posting.google.com...
> you are nearly correct John.....
>
> A Software Architect is a higher level position than a mere(!)
> programmer.
>
> not everyone that gets employed by a company to cut code will be
> equal. Skills come with experience, as do pay rises!
>
> At my company (a small software house), we have 3 Software Architects
> who are the gurus of the company, we then have maybe 7 senior level
> Software Engineers/Developer etc (like me), then about 3 lower level
> Developers.
>
> The lower level developers wouldnt have a clue as to how fit complex
> network/internet enabling technologies like Remoting or Web Services,
> how to design a database or why Stored Procedures are a good idea, or
> why Triggers can confuse people (like them!)
>
> The Software Architects are the ones that plan how the system is going
> to fit together on the larger "whole" scale. The senior developers are
> somewhere in between.
>
> :-)
>
>
>
>
>
> "John S" <John@notreallyhere.tv> wrote in message

news:<#nnUcceTDHA.1912@TK2MSFTNGP12.phx.gbl>... [colo
r=darkred]
> > > I think I failed because I don't have the experience
> > > as an architect !? I have been a developer...

> >
> > Should be considered the same title.
> >
> > Software Engineer, Software Practitioner, Analyst Programmer, Software
> > Developer, Software Architect are all the same.
> >
> > Software development is not just about slapping a few controls on vb
[/color]
form or
> > writing a bit of C# code. So maybe you should just give up or become
> > professionally competent in what you do for a living.
> >
> > "tommylee" <member32008@dbforums.com> wrote in message
> > news:3126931.1058544056@dbforums.com...
> > >
> > > Thanks, Emg.
> > > I will try that... I think I failed because I don't have the

experience
> > > as an architect !? I have been a developer...
> > >
> > > --
> > > Posted via http://dbforums.com



Jamie

2003-07-25, 8:23 am

yup, fair enough, but in your original email, you didnt mention
anything about grades or levels, you said all those titles were the
same.

With those grades comes levels of responsibility.

I agree with what you say about "Software development is not just
about slapping a few controls on vb form or writing a bit of C# code"
but as the grades/levels indicate, certain people arent ever going to
be asked to put together a UML diagram, to design a database schema,
map out where components are going to live on the network, decide when
a message queue should be used, decide whether we should use Biztalk
and many other SENIOR level decisions.

These are the people that wont climb the career ladder of titles which
programmers like u me have (eg. grunt -> jnr -> snr -> architect).

oh, and when i say "cut code" i mean typing in code into an editor,
not letting a case tool generate it! There are plenty of companies
out there who have people doing that, i'm sure you've seen plenty of
projects go tits up because no-one bothered to spec it or design it
properly just like i have.




"John S" <John@notreallyhere.tv> wrote in message news:<#aYFhw5TDHA.2188@TK2MSFTNGP10.phx.gbl>...
> No I am correct. They are just titles which mean the same thing. What your
> company describes as a 'Software Architect' is what my company describes as
> a senior (or principle) software engineer, another company my title that
> role as senior analysis programmer or designer. Naturally there are
> different grades which reflect the individual's experience and
> responsibilities, i.e. principle, senior, junior or just plan grunt.
>
> BTW, I don't know of any company that employs people to 'just cut code' -
> case tools do that.
>
> "Jamie" <j.mo@lycos.co.uk> wrote in message
> news:ce580daa.0307210557.3c46862@posting.google.com...
> > you are nearly correct John.....
> >
> > A Software Architect is a higher level position than a mere(!)
> > programmer.
> >
> > not everyone that gets employed by a company to cut code will be
> > equal. Skills come with experience, as do pay rises!
> >
> > At my company (a small software house), we have 3 Software Architects
> > who are the gurus of the company, we then have maybe 7 senior level
> > Software Engineers/Developer etc (like me), then about 3 lower level
> > Developers.
> >
> > The lower level developers wouldnt have a clue as to how fit complex
> > network/internet enabling technologies like Remoting or Web Services,
> > how to design a database or why Stored Procedures are a good idea, or
> > why Triggers can confuse people (like them!)
> >
> > The Software Architects are the ones that plan how the system is going
> > to fit together on the larger "whole" scale. The senior developers are
> > somewhere in between.
> >
> > :-)
> >
> >
> >
> >
> >
> > "John S" <John@notreallyhere.tv> wrote in message

> news:<#nnUcceTDHA.1912@TK2MSFTNGP12.phx.gbl>...
> > > > I think I failed because I don't have the experience
> > > > as an architect !? I have been a developer...
> > >
> > > Should be considered the same title.
> > >
> > > Software Engineer, Software Practitioner, Analyst Programmer, Software
> > > Developer, Software Architect are all the same.
> > >
> > > Software development is not just about slapping a few controls on vb

> form or

> > > writing a bit of C# code. So maybe you should just give up or become
> > > professionally competent in what you do for a living.
> > >
> > > "tommylee" <member32008@dbforums.com> wrote in message
> > > news:3126931.1058544056@dbforums.com...
> > > >
> > > > Thanks, Emg.
> > > > I will try that... I think I failed because I don't have the

> experience
> > > > as an architect !? I have been a developer...
> > > >
> > > > --
> > > > Posted via http://dbforums.com

dave

2003-07-25, 11:23 am

That's a lot of chiefs and not too many injuns!


>-----Original Message-----
>you are nearly correct John.....
>
>A Software Architect is a higher level position than a

mere(!)
>programmer.
>
>not everyone that gets employed by a company to cut code

will be
>equal. Skills come with experience, as do pay rises!
>
>At my company (a small software house), we have 3

Software Architects
>who are the gurus of the company, we then have maybe 7

senior level
>Software Engineers/Developer etc (like me), then about 3

lower level
>Developers.
>
>The lower level developers wouldnt have a clue as to how

fit complex
>network/internet enabling technologies like Remoting or

Web Services,
>how to design a database or why Stored Procedures are a

good idea, or
>why Triggers can confuse people (like them!)
>
>The Software Architects are the ones that plan how the

system is going
>to fit together on the larger "whole" scale. The senior

developers are
>somewhere in between.
>
>:-)
>
>
>
>
>
>"John S" <John@notreallyhere.tv> wrote in message

news:<#nnUcceTDHA.1912@TK2MSFTNGP12.phx.gbl>... [colo
r=darkred]
>> > I think I failed because I don't have the experience
>> > as an architect !? I have been a developer...

>>
>> Should be considered the same title.
>>
>> Software Engineer, Software Practitioner, Analyst
[/color]
Programmer, Software
>> Developer, Software Architect are all the same.
>>
>> Software development is not just about slapping a few

controls on vb form or
>> writing a bit of C# code. So maybe you should just give

up or become
>> professionally competent in what you do for a living.
>>
>> "tommylee" <member32008@dbforums.com> wrote in message
>> news:3126931.1058544056@dbforums.com...
>> >
>> > Thanks, Emg.
>> > I will try that... I think I failed because I don't

have the experience
>> > as an architect !? I have been a developer...
>> >
>> > --
>> > Posted via http://dbforums.com

>.
>

John S

2003-07-25, 12:24 pm

> I agree with what you say about "Software development is not just
> about slapping a few controls on vb form or writing a bit of C# code"
> but as the grades/levels indicate, certain people arent ever going to
> be asked to put together a UML diagram, to design a database schema,
> map out where components are going to live on the network, decide when
> a message queue should be used, decide whether we should use Biztalk
> and many other SENIOR level decisions.


My company expects the grads they take on to be able to correctly model
basic systems using UML taking use cases and producing the static and
dynamic views of the system. Where I work it is vital that people are
versatile and able adapt; as an example you will always be working on more
than one project, oftn doing different roles. If not, it means the company
is going down the drain becouse there is no work and no one wants our
products. In other words, we simply could not afford to have people standing
around waiting for 'someone to sign of the requirements specification'.

As far as detemining the 'most appropriate' technologies and approaches to
take, of couse only senior people make the top decisions. For us, this is
always undertaken by the technical project lead and other experienced people
(both from the technical and business area domains) in conjunction with the
customer. The customer(s) would soon dump you if you sent a grunt to do
this.

> These are the people that wont climb the career ladder of titles which
> programmers like u me have (eg. grunt -> jnr -> snr -> architect).


They would never be employed here.

> oh, and when i say "cut code" i mean typing in code into an editor,
> not letting a case tool generate it!


Working for a software house we tend to write code once and re-use it where
appropriate, both at the binary level and at the source code level (i.e.
templates and case tool generated skeleton code). We could not survive if we
did not have a process model in place which implied rewriting cod to do the
same thing over and over again. Less than ten percent of effort and
resources go into 'coding'.

> There are plenty of companies
> out there who have people doing that, i'm sure you've seen plenty of
> projects go tits up because no-one bothered to spec it or design it
> properly just like i have.


Fortunately not, we don't deal with cowboys [for long]. Although I know this
to be true as well - just look at the posts to this group - ha, ha!

"Jamie" <j.mo@lycos.co.uk> wrote in message
news:ce580daa.0307250408.1696dba2@posting.google.com...
> yup, fair enough, but in your original email, you didnt mention
> anything about grades or levels, you said all those titles were the
> same.
>
> With those grades comes levels of responsibility.
>
> I agree with what you say about "Software development is not just
> about slapping a few controls on vb form or writing a bit of C# code"
> but as the grades/levels indicate, certain people arent ever going to
> be asked to put together a UML diagram, to design a database schema,
> map out where components are going to live on the network, decide when
> a message queue should be used, decide whether we should use Biztalk
> and many other SENIOR level decisions.
>
> These are the people that wont climb the career ladder of titles which
> programmers like u me have (eg. grunt -> jnr -> snr -> architect).
>
> oh, and when i say "cut code" i mean typing in code into an editor,
> not letting a case tool generate it! There are plenty of companies
> out there who have people doing that, i'm sure you've seen plenty of
> projects go tits up because no-one bothered to spec it or design it
> properly just like i have.
>
>
>
>
> "John S" <John@notreallyhere.tv> wrote in message

news:<#aYFhw5TDHA.2188@TK2MSFTNGP10.phx.gbl>...
> > No I am correct. They are just titles which mean the same thing. What

your
> > company describes as a 'Software Architect' is what my company describes

as
> > a senior (or principle) software engineer, another company my title that
> > role as senior analysis programmer or designer. Naturally there are
> > different grades which reflect the individual's experience and
> > responsibilities, i.e. principle, senior, junior or just plan grunt.
> >
> > BTW, I don't know of any company that employs people to 'just cut

code' -
> > case tools do that.
> >
> > "Jamie" <j.mo@lycos.co.uk> wrote in message
> > news:ce580daa.0307210557.3c46862@posting.google.com...
> > > you are nearly correct John.....
> > >
> > > A Software Architect is a higher level position than a mere(!)
> > > programmer.
> > >
> > > not everyone that gets employed by a company to cut code will be
> > > equal. Skills come with experience, as do pay rises!
> > >
> > > At my company (a small software house), we have 3 Software Architects
> > > who are the gurus of the company, we then have maybe 7 senior level
> > > Software Engineers/Developer etc (like me), then about 3 lower level
> > > Developers.
> > >
> > > The lower level developers wouldnt have a clue as to how fit complex
> > > network/internet enabling technologies like Remoting or Web Services,
> > > how to design a database or why Stored Procedures are a good idea, or
> > > why Triggers can confuse people (like them!)
> > >
> > > The Software Architects are the ones that plan how the system is going
> > > to fit together on the larger "whole" scale. The senior developers are
> > > somewhere in between.
> > >
> > > :-)
> > >
> > >
> > >
> > >
> > >
> > > "John S" <John@notreallyhere.tv> wrote in message

> > news:<#nnUcceTDHA.1912@TK2MSFTNGP12.phx.gbl>...
> > > > > I think I failed because I don't have the experience
> > > > > as an architect !? I have been a developer...
> > > >
> > > > Should be considered the same title.
> > > >
> > > > Software Engineer, Software Practitioner, Analyst Programmer,

Software
> > > > Developer, Software Architect are all the same.
> > > >
> > > > Software development is not just about slapping a few controls on vb

> > form or
> > > > writing a bit of C# code. So maybe you should just give up or become
> > > > professionally competent in what you do for a living.
> > > >
> > > > "tommylee" <member32008@dbforums.com> wrote in message
> > > > news:3126931.1058544056@dbforums.com...
> > > > >
> > > > > Thanks, Emg.
> > > > > I will try that... I think I failed because I don't have the

> > experience
> > > > > as an architect !? I have been a developer...
> > > > >
> > > > > --
> > > > > Posted via http://dbforums.com



sumeshmcp

2003-08-28, 1:24 pm


Hi ,

I feel 70-300 is a tough exma. eventhough MS guide is really good i same
many really really tricky questiosn in some sample question papers.

So it will be agreat help if some one can give some suggestions and get
me a good dump.

Thanks

Sumesh


--
Posted via http://dbforums.com
Keith Nicholson

2003-08-28, 3:24 pm

Sure, justify it by cheating. Why not?

--
Peace,
Keith Nicholson, MCT, MCSD, MCAD



"sumeshmcp" <member37292@dbforums.com> wrote in message
news:3296024.1062084301@dbforums.com...
>
> Hi ,
>
> I feel 70-300 is a tough exma. eventhough MS guide is really good i same
> many really really tricky questiosn in some sample question papers.
>
> So it will be agreat help if some one can give some suggestions and get
> me a good dump.
>
> Thanks
>
> Sumesh
>
>
> --
> Posted via http://dbforums.com



Jamie

2003-08-29, 7:24 am

John s:
what u have described there John is the technical utopia!!

By the sounds of it, you work at a very successful software house and
good luck to you. If i started a company, i would want to hire the
best people coming in, people that could adapt, learn quickly etc etc.

The point i am simply trying to get across is that most places are
nowhere near as organised as that. I wish they were, then you wouldnt
hear about project costs rising, and projects failing all over the
place (and maybe there would be more jobs out there!)

You would also not have all the idiots saturating the market, by doing
a 1 years Masters IT conversion course, or believing that they can go
on a 12 week training course and then get a job as a programmer. Too
many companies have weak hiring processes, or will hire people just
because they are cheap.

I know, i know.... YOUR company wouldnt hire these kind of people, and
quite right too! all i am saying is that there are a lot of these
people around, and they get hired.




>My company expects the grads they take on to be able to correctly

model
>basic systems using UML taking use cases and producing the static and
>dynamic views of the system. Where I work it is vital that people are
>versatile and able adapt; as an example you will always be working on

more
>than one project, oftn doing different roles. If not, it means the

company
>is going down the drain becouse there is no work and no one wants our
>products. In other words, we simply could not afford to have people

standing
>around waiting for 'someone to sign of the requirements

specification'.

>As far as detemining the 'most appropriate' technologies and

approaches to
>take, of couse only senior people make the top decisions. For us,

this is
>always undertaken by the technical project lead and other experienced

people
>(both from the technical and business area domains) in conjunction

with the
>customer. The customer(s) would soon dump you if you sent a grunt to

do
>this.

john smith

2003-09-06, 8:26 am

If you really need a good dump, try adding extra fiber to your diet.


"sumeshmcp" <member37292@dbforums.com> wrote in message
news:3296024.1062084301@dbforums.com...
>
> Hi ,
>
> I feel 70-300 is a tough exma. eventhough MS guide is really good i same
> many really really tricky questiosn in some sample question papers.
>
> So it will be agreat help if some one can give some suggestions and get
> me a good dump.
>
> Thanks
>
> Sumesh
>
>
> --
> Posted via http://dbforums.com



Leigh Kendall

2003-09-06, 3:24 pm

ROFL... that's the best one I've heard in a long time!

Perhaps he should try http://www.metamucil.com. I hear they have good dumps
that he might find useful during his long stretches of hard studying <g>.

"john smith" <bgharvey@epix.net> wrote in message
news:%23MgG8yGdDHA.1932@TK2MSFTNGP10.phx.gbl...
> If you really need a good dump, try adding extra fiber to your diet.
>
>
> "sumeshmcp" <member37292@dbforums.com> wrote in message
> news:3296024.1062084301@dbforums.com...
> >
> > Hi ,
> >
> > I feel 70-300 is a tough exma. eventhough MS guide is really good i same
> > many really really tricky questiosn in some sample question papers.
> >
> > So it will be agreat help if some one can give some suggestions and get
> > me a good dump.
> >
> > Thanks
> >
> > Sumesh
> >
> >
> > --
> > Posted via http://dbforums.com

>
>


Sponsored Links





Free Braindumps | MCSE braindumps software forum

Copyright 2003 - 2008 examnotes.net