I hate to break it to you but o1 is like far off of anything what you describe. Yesterday, I was testing some stuff and told it in very precise prompt to write a dripping bucket rate limiting middleware and it just literally named a var “bucket” with a timeout and then implemented something that will wait for the next function to timeout!
I then said, heh and asked it to implement a circuit breaker pattern using axios, and it again implemented a timeout and added it to axios options!
Could be am dumb or o1 was hallucinating on me intentionally, but the thing is very far away from a Jr dev fresh out of college.
Feels like your Jr position claims 3 YoE in hardcore backend. Last time I’ve seen them, they discussed == vs === and “in” vs “of”. Wouldn’t hold my breath asking them to implement a rate limiter mw or any sort of debouncer. Unless humanity boosted their average intelligence very recently, ofc, where you’re an async networking specialist fresh outta school.
I think, my “very far away” was misunderstood. What I meant is that, a junior dev will hopefully go and do some research and try to find some reliable info before trying to implement something, while o1 just spits out statistical matches.
o1 is very far away from being a Jr dev replacement and is actually slightly more useful(if I ignore the costs entirely) than the existing intelligent autcomplete features.
Depends on the jr dev. You have the actual devs which develop solutions and the jrs who grow out to these roles. But I’ve been in plenty a company with just a bunch of code monkeys as well to write unit tests, boilerplate and center divs.
They are definitely being replaced by ChatGPT in our company. Think of it what you will, several teams write all their unit tests with ChatGPT now instead..
It is fine, if those terms are not relevant to you. We learn when we need to. My point was that, a Jr dev will do some research and then try to implement a solution, while o1 being praised as immediately replacement of Jr devs is not even close and only shows as much correct implementation as its training data.
I've seen a whole gamut of junior devs and their abilities. Your junior devs are just the average beginner. They still learn to get better, to become real devs. And we need real developers to deal with the stuff even o1 stitches together. Because you actually need to understand problems and code to solve problems. And even something like o1 is just a statistical model that outputs the most likely result based on an input. And I've seen the incoherent garbage it babbles out when it comes to code. But the main issue will be, the blind reliance on these hallucinating models that create 'just good enough' will hinder people from learning and becoming better. LLMs are the end of ideas. Just the calcified present. And that's a problem.
I would need to ask ChatGPT about what an PBI is, but other than that what do you expect. You don't learn coding in college, companies and devs need to train freshmen.
LLMs still cannot solve most logic problems. They generate language. It can be a programming language but obviously the scope is limited.
I swear to god, it’s better than our junior devs fresh out of college.
Like, I let the LLM solve a PBI and it’s just faster with better code.
Actual devs will still have a job, but the low hanging write some code guys? They’re done. And a lot of companies had a bunch of them..