This does unfortunately lead to a problem of people only getting hired for jobs exactly like what they've already done, so they no longer grow or gain experience.
Juniors would be completely screwed. But then, I guess they sort of already are.
You hit the nail on the head regarding Juniors—they are already in a tough spot, and I certainly don't want to build a tool that makes that worse.
However, my hypothesis is that matching on 'Problem Vectors' might actually help break the cycle of 'only getting hired for what you've already done.'
Transferable Complexity: A traditional recruiter sees 'Game Dev' and ignores them for a Fintech role. But a vector model might see that the candidate solved a 'distributed concurrency' problem in a game that is mathematically similar to the 'payment sync' issue in the JD. It matches on capability, not just domain keywords.
Signal for Juniors: Currently, ATS filters reject Juniors based on '0 years experience.' If a Junior has tackled a complex logic problem in a hobby project or Hackathon, this system highlights that specific signal. It gives them a fighting chance based on code reality rather than resume keywords.
That said, I agree this model naturally leans towards Senior/Specialist roles where specific technical gaps need immediate filling. It's not a silver bullet for 'hiring for potential,' but I hope it's a step up from the current keyword-soup approach.
We do mean AI being as an OS Functionality, although this has a long way to go and we transparently admit that we're still in initial stages. One of the primary use cases or functionality for AI integration would be for app development. The idea is to leverage AI by training an advanced model on our own data, thus making it capable to help developers port their existing software and applications to XenevaOS conveniently. Also it'll help beginner programmers create an app on XenevaOS from scratch easily.
App development wouldn't necessarily be the only functionality of AI in the OS but it will definitely be a primary one.
I don't understand why there are so many anti-monopoly suits against Google, Facebook, apple etc., when Amazon has been running with explicitly monopolistic policies for years without a word.
I would put forward that mdx is not a great choice of name, given that it already has a standard meaning in the markdown ecosystem: markdown with inline react components.
This sounds more familiar to me. xD
8 hour day, in a place with a nice or relaxed working culture that turns into 6 hours.
Minus lunch break, 5.
Minus meetings, 4.
Minus helping others, 3. Minus whatever procrastination during the day, in practice 2 hours on actual code.
I could see that going up to 5 depending on the working environment. But people answering 7+ hours seems bonkers to me, that's more than a working day!
Yup - if there was a camera today that could consistently (and without any fiddling) reproduce things the way my eyes see them (especially in high dynamic range or low light situations), I would buy it immediately!
One of the problems that plagues phones is that, if apple makes a change everyone else follows.
See it like this: Toyota arbitrarily declares that they'll disable any car without "Toyota" approved 30% taxed fuel. Then all the other car companies immediately copycat, seeing a new way to make money.
This is the case with iPhone and android. They do not have meaningful competition when they can just work together as a pseudo monopoly.
Juniors would be completely screwed. But then, I guess they sort of already are.
reply