HNHacker News
TopNewBestAskShowJobs

CPU_Verif

24 karma · joined November 3, 2016

submissionscomments
CPU_Verif··on Why hardware development is hard, part 1: Verilog is weird (2013)
In the first 2 years of work, I bounced about quite a lot within my first company, and did the following:

Formal proofs and checks for a full unit.

RTL design with another bloke on a block.

Owner of an testing tool (developer).

Owner of a testbench for top level design.

Owner of process for bringing up new pieces of RTL(4 blocks, one after the other) into the top level design.

All of this was caused because the startup I started in was stupidly undermanned, and there wasn't anyone else about. When I left that company, they had gone and hired about 12 people to do all of those tasks, and I saw myself handing over tasks to more senior people.

I had experienced atleast 3-4 different areas of the process, and became really familiar with ARMV8 (what got me my next job).

Yet this guy over here is thinking that its gonna take 2 years for someone to be even able to do 1 of those tasks?

Could argue a really long time about individual cases, but I think the Hardware industry has a very big problem with arrogance. Most companies and senior people carry an air of "no one else can do what I do" kind of bs, that I experienced in SV quite a bit. They look down on junior devs thinking that they are incapable of doing anything.

I asked in my office just now, the reasons for leaving their first jobs:

1. Wasn't allowed to do RTL design work inside the CPU

2. Wasn't given any responsibilities other than manually writing coverage(automating this was not permitted)

3. Ownership of the block that he had written from scratch was given to a more senior person once it came to integrating it to the top level

4. Money

I find it extremely common for people(usually at the 2-3 year mark) to leave for greener pastures where they are taken in as experienced engineers, rather than useless babes. It might be a rite of passage, or it might just be the mistakes of an industry entrenched in the past

CPU_Verif··on Why hardware development is hard, part 1: Verilog is weird (2013)
I'll throw in my opinion for this. The author states how its routine for people to be older in the Hardware Industry. I work as a Verification engineer for a CPU project.

From what I see, every company in this sector works off of years of experience. Even if you are god's gift to the world of CPU design, the career options available to your are linked to the years you have worked.

I recently attended a presentation by ARM, where they boasted of this quote "At ARM, we don't really expect our graduates to be able to do anything until they're about 2 years into their careers, at which point they're expected to be decent at something"

And they boasted of it! To a theater full of CS students. And this was a 35 year old line manager making the comment.

If you want a career where you can rise based on merit, and not the numbers of years on your CV, don't pick hardware. I've seen it as an insider, the occasional "kid" comment being thrown around(ARM), designers refusing to work with junior verif staff(imagination tech), people who have written a project from scratch over 2 years not given tech lead roles as the project grew, etc.

Such an enviroment quite often bleeds younger engineers. It saps desire and motivation. Because there are so few startups, good practices don't matter. Here's some conversations I've had:

"We don't need to write tests for our software ISG, its a waste of time" "What is wrong with me writing an extension to the software as a special case? It only executes that code if the username is me" "We don't do training for new people".

I routinely see younger engineers with 3-4 years of experience try and spin out of CPU/Hardware and into Software.