I debated on blogging on this site - debated for over a month. I was already doing something similar elsewhere, so why do it here? In my postings outside of Cadence, I did it because it was vendor-neutral, and I could speak my mind like an artist with no bounds, ask hard controversional questions about things about ASICs, AEs and the industry ecosystem without being slapped around. If I was going to post here, I wanted something similar or forget-about-it.
I had few questions before commiting to Tom to blog, our Cadence Community blog-master (who is a cool guy, I've found out). Here's what I asked him:
Me: Will you filter my blogs? (and I did check after my first few blog posts, to make sure no 'extra' edits were snuck in)
Me: Will you control me, like a puppet? Make me say things that give 'happy feelings' only?
Tom: Nope again. It's all yours dude to control.
Me: Will I lose my job if I type something someone doesn't like? (if I do, I think Jeff who recently posted something about "If Marketing People Lie?" would be in bigger trouble :) )
Tom: You shouldn't, but that's up to you. ;) (that's when I signed a legal form, stating that I'm responsible for everything I write, since it's not restricted)
- - -
So far, no signs of such things to report. Everything I've written is because I chose to. No catches. Amazing.
So why write? My vision is to share 'the life as an AE' from a designer's perspective, both the good and bad things I see from day-to-day. I used to be an ASIC design engineer in a number of start-ups and a large company, only recently dabbling in the AE life, and find life on the 'other side', the EDA vendor side, both interesting and challenging. I thought it would be interesting to give some tidbits here and there, each week or two, on things that I encounter, cool things that customers tell me, things that frustrate my customers - things like that.
Hopefully you find it useful, or at least somewhat interesting. :)