dick_freebird
Advanced Member level 7
As a 20+ year user of Cadence tools...
If you really want to be an engineer in the dictionary meaning of the word, you need to "look under the hood" to appreciate the compromises that are being made on your behalf in exchange for the higher level of abstraction at which Cadence force you to work. To do any real leading edge design (particularly analogue, RF or the real high speed digital stuff) you need to be able to work at a lower level of abstraction than Cadence offers.
I'd like to hear others opinions on non-cadence tools based on real use on products in production and in particular how they have solved problems that the cadence tools don't/can't.
SimonH.
I don't know where you get this stuff. I've been using Cadence
since it was called SDA and ran on MassComp 68K machines.
In that time, most of my work has been transistor level and I
have done my own models, PCells / device libraries down to the
polygon level and a whole bunch of analog and interface product
designs. Now maybe one or two had some level of "abstraction"
but not a one got by without me doing a lot of lowest-level
design, layout and in a lot of cases infrastructure work.
If you're "forced" to be abstract, look to your local CAD
bureaucracy and their flock of "methodology" harpies. The
tools are there for bottom-up work and nobody but your
own people, perhaps, requires you not to use them.
Now a lot of the cheaper tools do not have the option to
work at "higher" levels of abstraction and you'd have to
bring in your own point tools and integrate them. But it
is certainly not the case that Cadence prevents you from
going at it however deep you like.