Anyone have any inside knowledge about how bad this will be?
10 replies (most recent on top)
As a past DA... I can tell you. We don't want to write all the damn wrapper code, and we really really don't want to support it. But the methodologist who decide how we use the tools (who aren't DA's) reject the industry standards... and often even reject company standards. So not only do we have lots of wrapper code, we have lots of different wrapper code for the same tool, just different projects. Then lots of code to help those projects share each others data...
The source of the issue is the culture of appeasement. Someone asks for something, you should do it with very little question. It is how you do well come review time. If you make that person justify why they are doing things differently, they will say negative things about you and go to someone who will just do it. Thus things diverge.
What we needed was a stronger and more competent central tools and methodology team that architects a single way of doing things with some reasonable variation.
Who knows, maybe that is what they will do... probably not, but maybe if they just fire all of the methodologists and DA's, the new people will be forced to use industry standard methods because they don't know any others...
I thought the same thing, why do we have a DA org. I came from chip company to Intel 2 years ago and I wanted to contact Synopsys support on an issue and was told no you need to go through first line DA and then they contact DTS who talks to Synopsys. I was like seriously? At my company we had Synopsys AE on site to help, why does Intel pay people to Synopsys work... dude AE support comes with the tool!
Why do we need DA group ? To ease eda tool usage ?
If so it is may designers are stupid...
Btw in sw do they use some wrappers ? .. aka build tool.. makefile..to ease building a component, a full product.. and even automate tests for these builds...
Do you think that sw developer call compiler command line natively ? Or even test framework..
Strange that sw peolple use automation for their tasks. But hw people wont need that ..
Amen....design automation staff should be cut by 90% or more. Why do you need such extensive wrappers on industry tools.
Yep this is true, get rid of many of the internal development which duplicates industry tools, get rid of the 1000 of lines of perl scripts wrapping vendor tools and leverage tool vendors like all others do to centralize support. I would expect 30% - 50% HC reduction across DTS and DA teams in PEG
Gawd! The least they can do is let us catch our breath. At least it's never boring in PEG!
Yes, it will be announced soon. but this model won't work well which happened too many times in the past when they wanted centralize it.
Rearranging deck chairs as we say
DTS has been in restructuring since many years back. Kept moving around different groups.
I heard about this. Why would they reorg right in the middle of the layoffs - bizarre. Sounds like they are in a panic state.