2 ms·
>By 'real electronics' they probably mean high frequency or very high speed designs, a GPU card manufacturer say. I duuno man, at a startup I worked at, the gr
by FirmwareBurner 3y ago
>By 'real electronics' they probably mean high frequency or very high speed designs, a GPU card manufacturer say.
I duuno man, at a startup I worked at, the graybeard EE was doing 2.4GHz RF design on software cheaper and more rudimentary than Altium, let alone Cadence.
So I'm always rolling my eyes when someone uses the world "real" as some sort of macho flex with vague meaning like "real men", "real work", "real engineering", "real software development", as if only their particular example makes the world go round and scoff at everything else like it's unimportant child's play.
- vanchor3 3y agoSure, you can do 2.4GHz on a 2 layer board with even the simplest programs, or even Inkscape really. The hard part is arguably knowing the write math involved to design with signal integrity in mind. When you start working with very high speed things like DDR4/DDR5 on 14 layer boards you could do it with simpler software, but I don't see why you would. The time saved with the design tools and signal integrity simulations would likely be worth much more than the licensing cost, especially if you're bigger than a small hobby shop. Not to mention the money saved on having software that can identify mistakes early on when the PCBs alone can cost thousands. And then there's all the other bits like conforming to standards, providing deliverables in a format that the next place down the line deems "acceptable" (or they're just picky), as interoperability with other teams, because sometimes you're just one small part of the design process.