Phil Kane wrote:
On Mon, 01 Oct 2007 03:24:02 -0700, wrote:
- Do you know what VHDL is?
- How about a state machine?
- Synchronous DDR?
- PCI Express?
- Flip-flop?
- What does GCLK mean in the context of FPGAs?
- What are constraints?
That's not electrical engineering, that's computer science.
And thus you make yourself sound like an idiot. Hardware design is
*not* computer science (aka programming). ------ Besides my title is
"Electrical Engineer". Always has been, no matter where I worked.
This is just a small sample of what I know, because this is what I
work upon every day..... but I suspect a lot of it you have no clue
what it's about. And that's fine. Because I don't expect one person
to know everything there is to know about EE.
Not to denigrate Penn State, but graduates of the major EE (as
differentiated from CS) schools are expected to be fluent in most if
not all areas of ELECTRICAL engineering. ...
That sounds like a denigration of Penn State. They did teach me all
the basics, but not the advanced stuff (like synchronous AM reception
- whatever that is). To expect me to know that is unrealistic. And
not fair to the profs at Penn State. Every engineer has his or her
own specialty.
I'm registered as a PE (Electrical) in four states... I am also
licensed to practice law in all California and Federal courts
Wow. I'm impressed.
I passed the E.I.T. exam back in 1998, but never bothered to register
P.E. because I don't see any value in it. I'm still getting paid $55
an hour, and having a P.E. after my name is not going to drive that
Rate any higher.
Same with a Masters Degree. If I thought there was value in having
those, then I would go ahead and acquire them, but so far they've been
not necessary.
So how do you like law?
I was thinking about going back to earn a law degree (since I'm bored
with engineering).