81–90 of 117 posts
Earlier quoted context omitted.
Please don't use human slurs for computer programs you don't like.
Why are we defending the feelings of chatbots? Does the word clanker upset you too?
It’s not good for your mental health.
Earlier quoted context omitted.
I agree with the sibling comment and also don't understand how the title is "offensive". I literally can't think of anything that could be offensive about any term in the title or the title as a whole.
It's the logic that is offensive. Mimically restated - The title isn't incorrect but it won't be misunderstood by few. A synonym for offensive is disgusting.
There's a very strong narrative in the zeitgeist that "no one" is hiring entry level jobs anymore because they're being replaced with AI. There's some pretty solid hiring data for CS grads, at least, that backs this up, even when controlling for the down economy as a whole.
So the first part "Not hiring junior engineers" is very clear. Whatever this blog post is, it's a message to companies that are making these hiring decisions.
Then, the rest follows: " won't work". It won't solve the problem you think you have.
Now that I've got your perspective, it IS possible for me to force my brain to incorrectly parse the title in a way that produces word salad, so I guess I can get it.
I had all the context I needed to easily grok it at first glance. The intended audience of the article (people who are deciding to hire fewer junior engineers) ALSO probably have that context. But it's not hard for me to believe that there are lots of people even on HN that didn't!
Thanks for clarifying
Earlier quoted context omitted.
Yeah, you need to learn the jargon, and then use that to ask the agent to debug its own output. Sometimes you can get away by asking the agent to do the web searches and get it to figure out the stuff on its own. Again, it's not zero effort, but it's no longer skilled work.
The point of my comment is that it's absolutely skilled work. If someone with 15 years of experience in programming can't simply make a lateral move into a different type of programming without falling on their face, then it means there's more than just jargon. Each problem domain has its own unique nuances that humans need to tease out, and that requires domain skills.
I'm not sure I understand the logic that we wouldn't hire Juniors because now we have AI. What jobs are Juniors doing that AI can now do? I don't get juniors to build me entire web sites or implement complicated agentic pieces of work. Most of the time, we hire Juniors to help fill the talent pool with the hope that they will be productive in a few months. If we think that we don't need to refill the pool now because…
At least with AI if it's not working out you just shut it off and it's done. If it's a person's livelihood that process takes a huge burden on all involved.
I'm not sure I understand the logic that we wouldn't hire Juniors because now we have AI. What jobs are Juniors doing that AI can now do? I don't get juniors to build me entire web sites or implement complicated agentic pieces of work. Most of the time, we hire Juniors to help fill the talent pool with the hope that they will be productive in a few months. If we think that we don't need to refill the pool now because…
I used to use the new hires to hold expertise so that I can spend a weekend at the beach without getting paged. That was the true selfish incentive in spending negative productivity where it takes me more time to teach than to do.
AI absorbs knowledge that the company can keep when I leave.
This used to be a capacity and bandwidth issue, as well as a timing issue with spare time.
I couldn't spend 9 PM to 11 PM on an odd Thu doing this with a human.
Earlier quoted context omitted.
> Seniors don’t use SO anymore Did they ever? SO wasn't around during my junior days so I never got to experience it from that angle, but it looked like it would have been an incredible resource for those who juniored in its heyday. However, I never found it to be successful in delivering to the problems I encountered as a senior.
Right, SO was always better at answering beginner questions then advanced ones, except if the complex question had a broad appeal. Part of it is because the format is not good for asking a context-heavy question. Another part because you were dependent on the pool of people answering, and the more niched the question was (using a library not very popular, for instance) or the more expertise it required, the less like…
very hard for junior engineers out there now.
There are too many new grads and the quality bar outside of target programs has dropped nor never existed to begin with. And the target programs graduate around 15-20k EECS adjacent majors a year. It's hard to justify hiring a (choosing random college) CS@Ouachita Baptist University grad for $140K TC (50th percentile for an entry level SWE) or even $100K TC [0] (25th percentile for an entry level SWE) unless they are…
Earlier quoted context omitted.
There are too many new grads and the quality bar outside of target programs has dropped nor never existed to begin with. And the target programs graduate around 15-20k EECS adjacent majors a year. It's hard to justify hiring a (choosing random college) CS@Ouachita Baptist University grad for $140K TC (50th percentile for an entry level SWE) or even $100K TC [0] (25th percentile for an entry level SWE) unless they are…
At least in 2020 when I was in this pool, the rate for recent grads from an average program was $75k-$85k
When I started as a SWE my TC was around $150K and that was in the early 2010s.
And the Levels numbers line up with new grad salary bands from back in 2019-20 as well.
Of course there is also a regional factor, but regional mobility has always been high at target programs (eg. It doesn't matter if you live in Seattle, San Francisco, or NYC but everyone will know UT Austin or Purdue).
Earlier quoted context omitted.
The literal meaning of the word is "delayed", which seems less descriptive than the words you rejected in https://news.ycombinator.com/item?id=49183728 . Do you understand why this word is "forbidden"? What's the advantage over a more vulgar word like "fuckwit"?
[dead]
> “That movie was so developmentally disabled”.
Nobody says this, and it's been 14 years since this article was published. The euphemism treadmill continues up until people stop treating the attribute as slur-worthy – which was the primary goal of this campaign.
> For that reason I think these comments are going to stick with people once they leave this comments section.
No, this is going to stick with me, because it's an attitude that I find exceptionally annoying: constantly repeating "I have a noble cause, therefore I am in the right", when you've already said it once. I'm reasonably confident I'm going to forget the details of your message by the end of the week, because you are far from the only edgelord on the internet, and you all go into my mental bucket of "not worth listening to", but I will remember that you were obnoxious about whatever it is you were saying.
Earlier quoted context omitted.
Well. I own my business and I really hate this attitude that some startups executives have. I want quality. Not blind speed. I want speed to be a by product of a well built product and a system that builds it. Not a bunch of slop thrown over the wall that I have to then debug and fix.
The AI is pretty good at debugging and fixing it. It's quite a bit better at it than writing the code, to be honest. And, you're right, I used to enjoy my job a lot more before AI. But in the end, the paychecks keep coming, and I can produce a lot of acceptable code quickly with little skill. Skill in coding no longer makes economic sense.