[flagged]
Interesting how titles alone has been getting the front page recently.
Becoming a compiler engineer
131–140 of 160 posts
Re: Becoming a compiler engineer
#132The comments are wildly fragmented in this thread. I agree with @torginus, the article has less and less of anything useful to people that want to get into compilers. Anyways, the "Who .. hires compiler engineer?" section is fairly vague in my opinion, so: AMD, Nvidia, Intel, Apple, Google definitely hire for compiler positions. These hire fairly 'in-open' so probably the best bets all around. Aside from this, Jane S…
> but for that certain language
What do you mean by that?
Re: Becoming a compiler engineer
#133Earlier quoted context omitted.
Sure if you want to build a lisp clone. Anything else, you're better off starting off with LLVM. Especially if you want a compiler job.
I've got compiler jobs without ever touching LLVM. Even gcc has a better codebase and performance. If just its maintainers would behave as nice as the LLVM maintainers who are really nice. Eg with gcc you can write a jit in pure C. With LLVM you'd still need C++ for name lookup hooks. With qbe you won't need any of this. With lisp much less.
Yes, I'm sure you got a compiler job without touching LLVM.
Doesn't mean it's good advice for someone getting into a field where LLVM is the technology used for 90% of the jobs.
Re: Becoming a compiler engineer
#134Earlier quoted context omitted.
It was supposed to be out years ago! She got a substantial advance but presumably delayed it due to the plagiarism scandal
> plagiarism scandal Do tell
From one of the publishers she worked with - https://www.halfmystic.com/blog/you-are-believed
Re: Becoming a compiler engineer
#135Earlier quoted context omitted.
Elaborate on this. Is it not sad when a UIUC Or Perdue grad can’t get a compiler engineer job out of undergrad? What does it mean to be cooked?
Rephrased: If a graduate with relevant coursework from a top institution struggles to find a job in a particular field, what sort of chances do the rest of the graduates from less known colleges have? It makes sense now, doesn't it?
UIUC and Perdue are not lesser known than MIT. Big state schools are roughly as known they just don’t have the same signal for being a superhuman.
Re: Becoming a compiler engineer
#136[flagged]
> This is a personal puff piece. Seriously? She's posting on her personal blog (that's what her substack is). Up front she says that one of the two kinds of people she's writing for are those who are interested in her personally. > she needn't use There are a lot of things that people needn't do, like absurdly talk about "attack vectors".
I might have been a bit harsh in how I phrased it, however if it's just a personal blog post, it does not belong on HN. I don't think most people here are interested in strangers' personal lives.
If it was her who posted it, she should've made it more clear that this is a 'personal journey' post. If it was someone else without her permission, then that should've not done so.
If you look at most of the discussion that emerged around it, it's about the relative technical merits of various compiler frameworks and techniques, and getting a job working with compilers, which I think most people expected to read about.
Re: Becoming a compiler engineer
#137Earlier quoted context omitted.
Sure if you want to build a lisp clone. Anything else, you're better off starting off with LLVM. Especially if you want a compiler job.
I've got compiler jobs without ever touching LLVM. Even gcc has a better codebase and performance. If just its maintainers would behave as nice as the LLVM maintainers who are really nice. Eg with gcc you can write a jit in pure C. With LLVM you'd still need C++ for name lookup hooks. With qbe you won't need any of this. With lisp much less.
You got me to check out GCC and QBE, and I say, not having to bother with SSA does seem to make things a bit easier, with GCC's Gimple being a kind of pseudo-assembly language, and Generic being almost C.
Still I think once you get over the hurdle of SSA-ifying your procedural code, LLVM is all right, and seems to be a lot more feature rich (I might be stupid, but I don't see how to make stack maps in GCC).
Also GCC is very lightly documented while LLVM seems to have quite good docs and tutorials.
Re: Becoming a compiler engineer
#138Earlier quoted context omitted.
> This is a personal puff piece. Seriously? She's posting on her personal blog (that's what her substack is). Up front she says that one of the two kinds of people she's writing for are those who are interested in her personally. > she needn't use There are a lot of things that people needn't do, like absurdly talk about "attack vectors".
I might have been a bit harsh in how I phrased it, however if it's just a personal blog post, it does not belong on HN. I don't think most people here are interested in strangers' personal lives. If it was her who posted it, she should've made it more clear that this is a 'personal journey' post. If it was someone else without her permission, then that should've not done so. If you look at most of the discussion that…
There's so much wrong with this ... no it wasn't her who posted it, and no one needs her permission to do so. (And how do you know that they didn't get it?) And if it didn't belong on HN then it would have been flagged and killed. It wasn't because it isn't just about her personal life--it has useful and appropriate content for readers of HN. again, up front she says that there are two kinds of people she's writing for. (Even then, the "personal journey" aspects of the article are largely relevant for HN readers interested in being compiler engineers.)
And do you really have no sense of how utterly absurd
> she needn't use the title of 'Becoming a Compiler Engineer' as an attack vector
is? Her title is perfectly reasonable and beyond any rational sensible intellectually honest good faith criticism.
The fault you seek lies entirely within.
Re: Becoming a compiler engineer
#139[flagged]
> Her accomplishments are impressive and well deserved what exactly are those even? that she went to MIT? from her linkedin she's at some blockchain startup (for only 4 months) doing "compiler work" - i put it in quotes because these jobs actually happen to be a dime-a-dozen and the only thing you have to do to get them is pass standard filters (LC, pedigree, etc.).
The article says
> I was a compiler engineer at a startup in New York City. In that role, I worked on extending a preexisting open-source programming language.
> I am now a compiler engineer at a large, post-IPO tech company in the San Francisco Bay Area. I work on making programming languages run faster.
The 4 month startup is the former.
Re: Becoming a compiler engineer
#140Earlier quoted context omitted.
> That means the general expectation is not that it is never a rehash of existing ideas. There’s a different from rehashing existing ideas and copying multiple passages off as your own. > If that is true, it sounds certainly fishy, but that is a case of violation of copyright and intellectual property and not of plagiarism. What exactly do you think plagiarism is? Here’s one common definition: “An instance of plagiar…
> What exactly do you think plagiarism is? Here’s one common definition: Both are about passing of something of your own. Plagiarism is about passing ideas of insights of as your own. It doesn't really matter, whether you copy it verbatim, present it in your own words or just use the concept. It does however matter how important that idea/concept/topic is in your work and the work you took it from without attribution…
>I have taken from the comments that it was only the case, that she rehashed ideas from other books, and I wanted to point out, that while this is a big deal for academic papers, it is not for books and basically expected.
In addition to near verbatim quotes, she is also accused of copying stories beat for beat. That's much different than rehashing a few ideas from other works. It is not expected and it is very much considered plagiarism by fiction writers.
As for the quotes she copied. That is likely both a copyright violation and plagiarism.
Plagiarism isn't just about ideas but about expressions of those ideas in the form of words.
Webster's definition:
"to steal and pass off (the ideas or words of another) as one's own : use (another's production) without crediting the source"
"to commit literary theft : present as new and original an idea or product derived from an existing source"
Oxford learner's dictionary:
"to copy another person’s ideas, words or work and pretend that they are your own"
Copying verbatim or nearly verbatim lines from a work of fiction and passing them off as your own is both plagiarism and copyright violation.