[flagged]
[flagged]
It's incredibly rude, and wrong, to assume that a woman was hired because she "checks off a bunch of HR checkboxes" rather than skill or hard work when you know nothing about her.
Becoming a compiler engineer
81–90 of 160 posts
Re: Becoming a compiler engineer
#82Not many companies are willing to maintain a compiler... but LLMs will change that. An LLM can find bugs in the code if the "compiler guru" is out on vacation that day. And yes, you will still need a "compiler guru" who will use the LLM but do so at a much higher level.
For that, they would need to make LLMs not suck at easy programming tasks. Considering that with all the research and money poured into it they still suck at easy stuff, I'm not optimistic.
Re: Becoming a compiler engineer
#83Earlier quoted context omitted.
LLMs (or LLM assisted coding), if successful, will more likely make the number of compilers go down, as LLMs are better with mainstream languages compared to niche ones. Same effect as with frameworks. Less languages, less compilers needed.
See, I'm coming from the understanding that language development is a dead-end in the real world. Can you name a single language made after Zig or Rust? And even those languages haven't taken over much of the professional world. So when I say companies will maintain compilers, I mean DSLs (like starlark or RSpec), application-specific languages (like CUDA), variations on existing languages (maybe C++ with some in-hou…
Yes, several, e.g., Gleam, Mojo, Hare, Carbon, C3, Koka, Jai, Kotlin, Reason ... and r/ProgrammingLanguages is chock full of people working on new languages that might or might not ever become more widely known ... it takes years and a lot of resources and commitment. Zig and Rust are well known because they've been through the gauntlet and are well marketed ... there are other languages in productive use that haven't fared well that way, e.g., D and Nim (the best of the bunch and highly underappreciated), Odin, V, ...
> even those languages haven't taken over much of the professional world.
Non sequitur goalpost moving ... this has nothing to do with whether language development is a dead-end "in the real world", which is a circular argument when we're talking about language development. The claim is simply false.
Re: Becoming a compiler engineer
#84Earlier quoted context omitted.
What I just said is a fact. Look it up if you like
No I'm literally saying - she writes fiction- how can you plagiarize a fiction book and make it work lol (I have no knowledge / context of this situation - no idea if she did or what happened here)
You don't seem to know what plagiarism is.
Re: Becoming a compiler engineer
#85In truth we need a curriculum to help people learn how to become compiler engineers.
Hands-on balanced with theory.
We need more compilers (and interoperability of course) and less dependence on LLVM.
Re: Becoming a compiler engineer
#86RIP my dreams of becoming a professional parentheses balancer
Re: Becoming a compiler engineer
#87This is an old content and reposted in this article.
Re: Becoming a compiler engineer
#88Made an account to say thank you for sharing this post (and to Rona Wang for writing it)! I stumbled into having an interview for a Compiler Engineer position coming up and I wasn't sure how to prepare for it (the fact that I got this interview just goes to show how little people really know about Compilers if they're willing to take a chance on a normal C++ dev like me hah) and I had absolutely NO idea where to even…
are you sure the content of the article is from some other article, quite a old one. as far as i remember
Re: Becoming a compiler engineer
#89I feel like the comments are too negative here. Yes, it may not be a step by step guide, but for niche roles like this, I feel no such guide could exist and only self study and some company taking the opportunity on you are the only ways in which one could get a systems/low-level job.
Re: Becoming a compiler engineer
#90Is this an ad or something? I was hoping for technical details :(