I guess I'll be the first to say it - does the author of the article strike anyone as a bit of a pretentious asshole? Downvote away if you have to, but I just thought someone needed to say that.
The FPGA Designer Who Didn't Get the Job
51–60 of 93 posts
Re: The FPGA Designer Who Didn't Get the Job
#52Earlier quoted context omitted.
No.
It depends on what you see as canon. From Arm 2:9-21, > And Saint Attila raised the hand grenade up on high, saying, 'O Lord, bless this thy hand grenade, that with it thou mayst blow thine enemies to tiny bits, in thy mercy.' And the Lord did grin. And the people did feast upon the lambs, and sloths, and carp, and anchovies, and orangutans, and breakfast cereals, and fruit bats, and large chulapas. And the Lord spak…
Re: The FPGA Designer Who Didn't Get the Job
#53If you found this article interesting, I'd recommend this article by the same author: https://zipcpu.com/blog/2020/11/26/zipcpu-biz.html > On another team I worked with, I was asked to call a man by female pronouns. This one brings me more grief, as I enjoyed working with the individual in question. He wanted to declare himself to be a woman. He changed his name, his clothing, his looks, his dress, you name it. While…
Damn, for all the huffing and puffing about “prima-Donnas”, it sure sounds like this guy couldn’t even follow a very reasonable request.
Re: The FPGA Designer Who Didn't Get the Job
#54Earlier quoted context omitted.
> You don’t get to redefine language and force your linguistic preferences on others. That’s not how language works. I don't particularly care about rehashing the ethics of preferred pronouns right now, but what you've described is exactly how language works. You might look into why standard practice moved away from capitalizing nouns in the 19th century.
Deutsch is keeping the faith in the twenty first century!
English is like easy mode for inclusion.
Re: The FPGA Designer Who Didn't Get the Job
#55I guess I'll be the first to say it - does the author of the article strike anyone as a bit of a pretentious asshole? Downvote away if you have to, but I just thought someone needed to say that.
Re: The FPGA Designer Who Didn't Get the Job
#56Re: The FPGA Designer Who Didn't Get the Job
#57If you found this article interesting, I'd recommend this article by the same author: https://zipcpu.com/blog/2020/11/26/zipcpu-biz.html > On another team I worked with, I was asked to call a man by female pronouns. This one brings me more grief, as I enjoyed working with the individual in question. He wanted to declare himself to be a woman. He changed his name, his clothing, his looks, his dress, you name it. While…
From another post: https://zipcpu.com/blog/2018/10/04/welcome.html > My Christian beliefs are centered around a literal interpretation of the Bible. This includes a belief in a 6-day creation that took place roughly six-thousand years ago, a belief that God will cause the end of this world rather than any man-induced climate change, a firm belief that a free people should be an armed people, and more. Ouch.
Re: The FPGA Designer Who Didn't Get the Job
#58This shouldn't have been too shocking. In the digital design industry, design engineers and verification engineers really are different positions. They require different skills, and though there are people who can do both well, they haven't been interchangeable for a few decades. I'm not surprised that an applicant for a design position would decline a verification job, especially if they're not just looking for an entry point at some prestigious team like Apple's CPU group.
The strange thing is that finding a bug and "fixing a broken design" is a design task, not a verification task. The verification engineer creates the simulation testbench and the tests to expose bugs. The design engineer uses these to find and fix the bugs. I doubt that most design applicants would balk at being asked to find and fix a bug in an existing design. So I'm not really sure exactly what he asked the interviewee that got the response he claims.
> One of the realities ingrained in the history and culture of Gisselquist Technology is that simulations rarely find the critical bugs.
This statement is so wrong that I think the author must have decided to redefine "critical bug" as any bug that simulation doesn't catch. In reality, there are critical bugs found at multiple steps -- design review, simulation, prototyping, ... not to mention critical bugs found in backend "verification" (timing analysis, equivalence checking, ...). The author pushes formal verification but it's not an alternative to simulation; it's a complementary strategy.
Re: The FPGA Designer Who Didn't Get the Job
#59I guess I'll be the first to say it - does the author of the article strike anyone as a bit of a pretentious asshole? Downvote away if you have to, but I just thought someone needed to say that.
Repeated “formal methods” but I never learned what that meant, by the end of the article.
Re: The FPGA Designer Who Didn't Get the Job
#60I guess I'll be the first to say it - does the author of the article strike anyone as a bit of a pretentious asshole? Downvote away if you have to, but I just thought someone needed to say that.
This is probably the most important line of the post for context. The latter 70% is a copy/paste of an email response he sent to a job applicant who said he wanted to do design, not verification. Presumably this copy/paste is almost the entirety of his response because the post ends the way you would expect an email to end, with a signature.
I don't know the full situation, but I'm imagining the candidate said "not quite what I'm looking for" and got this guys life story in response, along with insinuations that he's a Prima Donna, and judgments like "If you are a design engineer who can’t humble himself enough to verify a broken design that’s been given to you, then I foresee that you will also be difficult to manage."
He might be a nice guy, I don't know. But from what I see of this interaction, he was acting like an asshole.