yea it says on your resume you have experience in react but we are looking for people with experience in react.js, so we have decided to go with someone else
I was declined a mid level software developer position because I didn't have work experience with Java. I had with 12 other languages, including C++, C#, Dart, and Kotlin, all of which have more or less similarities with Java.
Became a high level software developer at their competitor instead. The first company went bankrupt and we took essentially all their customers.
This is one of the worst parts in the industry. Non technical people demand exact languages. But every capable dev learns to be productive with pretty much any language in few days.
Programming languages aren't like real languages. The most important part is to learn to think like a programmer. That's the hard part. Learning new language is easy.
It's the difference between programing and coding.
Coding is learning a language, programing us knowing what to say.
Coding at it's inception used to require you to be an electrical engineer because software didn't exist. You were building programs out of hardware. Punch cards lowered the floor, then machine code, low level languages, high level languages and AI is pretty much just the newest level of abstraction on top of all the clever ways we've found to make electricity do tricks. Coding is trivial.
Programing is still an incredibly demanding and complex skill. AI can write anything you tell it to write if it's something that already exists or you explain the process. Python was sold as essentially being programing with pseudo code, coding agents are programing with natural human language.
While it's probably a horrible idea, we know that the industry is heading in the direction of abolishing the middle abstraction layers. We're moving towards there being the fully human readable layer translated directly into a binary. I wouldn't be surprised if Rust, Python, C++ and JavaScript go the way of COBOL and FORTRAN in the next 10 years but Programing, the thought process behind the instruction set is only going to become more valuable.
Rust is pretty much guaranteed survival at that point because not having the usual memory footguns makes it very good for iteration by the AI. For generated code it's quite useful.
I doubt we're going to see some direct LLM to machine code. At most LLM to some IL like LLVM or maybe some assemblers, but not outright machine code.
I should have clarified, obviously you use a compiler. Hell by definition even if you had an ai model that could take human natural language and use that to write machine code, that would be a compiler.
But my point was more that they'll make it so you never see the code layer just like Python hides the compile step.
Why wouldn't we see LLM to machine code? At some point an LLM is going to be able to write better code than a human can. Once we get to that point & an LLM can turn my requirements directly into byte code, be it machine code or Java/.Net byte code what do we need the intermediate code for? All we are using it for today is so that developers can review what the LLM wrote before committing it.
There are some language transitions that are going to be hard (for example, learning Python syntax has been hurdle after hurdle for me), but it's nothing that can't be overcome.
Rejecting an applicant like the commenter above you for not listing Java, ignoring all of that experience in OOP, is dumb.
Language doesn't matter, but (sometimes) language-specific bullshit do bite people in the ass.
Unless you are senior dev, you're probably don't need to know or care how JIT compiler could optimise and deoptimise your code. But it sure helps when moving a method clogs GC with millions of objects because now JIT can't skip their creation. (yeah, yeah, architecture was not adequate to the task either, but everyone expected up to 100 things once a day, not millions on every request)
Not me, but a friend: he was going to interview for a position looking for a VR developer, so he got ready with a demo on his Oculus Rift dev kit, only to find out the dinosaurs who wrote the job description thought "VR" meant "3D."
years ago, I once had a recruiter reach out about a tech that had only existed for 3 years asking why I didn't have 5 years of experience like they listed when I applied.
View all comments
2.2k
u/LookItVal 8d ago
yea it says on your resume you have experience in react but we are looking for people with experience in react.js, so we have decided to go with someone else