Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Which is Better- Circuit Design OR Layout Design?

Status
Not open for further replies.

lohitha

Newbie level 4
Joined
Aug 1, 2012
Messages
7
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Location
bangalore
Activity points
1,339
"I just want to know which field is better? circuit design or layout design and why?"
please provide some justification points...
 

A true engineer considers many aspects of engineering to be interesting, even outside their specific field. If you find one or the other "better" then explore that aspect. The question is like asking is a train conductor better than a rail repairer. I doubt either would be working if the other stopped.
 
it is purely based on your mindset

some will have an interest in a field and they may have strong views why theirs is the best but others may not find it the same

it is no use giving into others intentions and then blaming that the path chosen is not of your taste

explore your field of interest and you yourself will find which is better and why

all the best in your selection
 
  • Like
Reactions: eng_ema

    eng_ema

    Points: 2
    Helpful Answer Positive Rating
I prefer to "own" my design front to back. If you're going to decide
you only will work on one piece, then you are just a cog in the
machine. Now in that scenario, the cogs closer to the front seem
to get all the grease. But you also have to be good at abstract
stuff, in hopping on the latest tool before it gets popular, and at
making your abstract BS seem like it's actually a source of value
rather than a tax, if you want to advance. Working the back end
you're pretty much assured of work, provided you demonstrate a
very, very low rate of screwups and decent throughput and low
need for constant coaching / correction.

None of these are known in your present situation, so the only
useful advice is "things to ask yourself".

That, or golf with your boss's boss.
 

In reality, you need to learn both to appreciate the subtle effects of hidden non-ideal equivalent circuit of your components and how layout will affect it so that you can specify where to locate EMI chokes, filters and how to minimize crosstalk in coupling fast edges to high impedance signals.
 
provided you demonstrate a very, very low rate of screwups
Hehe or, if there are screwups, ensure that you're the guy seen to be fixing them (with high visibility), so that everyone congratulates you on being the problem-solver and forgets that you caused it in the first place ; ) Not sure it would work many times, but you never know!
 

Hehe or, if there are screwups, ensure that you're the guy seen to be fixing them (with high visibility), so that everyone congratulates you on being the problem-solver and forgets that you caused it in the first place ; ) Not sure it would work many times, but you never know!

the better would be you not showing to much off when you solve stuff if new scenario arises you may be in a very tight corner and always the saying "TOAD SPOILT BY IT'S MOUTH"
 

Schematic designer needs to be fully responsible for the layout inspection and faults in production from BOM substitutions. So he needs to sign for BOM with alternate sources , layout and production fabrication rules and test criteria. This all comes down to writing a good SPEC {Before you start designing} so that everyone understands the theory of operation, test specs .. and you know how to design it and then validate the prototype against environmental stress limits and the production unit against material and assembly variations. A good spec does not need to show how the design is implemented as much as it needs to define the interface signals and what they do.

This is my layman's description, but the designer must drive the team of participants to make the end product successful.. THe program manager makes sure everybody has what they need to not slip schedule or budget which is your responsibility. Always overestimate this process until you get some mileage under you and learn how to do things more efficiently.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top