The irony of using a chatbot to gain insight into the current problems with the job market
Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
91–100 of 173 posts
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#92Been there. Hackers will do what hackers will do.
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#93LLMs aren't reliable for actual number crunching though (at least from what I've seen). Which is why I really appreciate seeing this blend!
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#94Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#95Nit: There appears to be both MongoDB and Mongo in the database graph.
Also, could you do a write up on how you actually used GPT-4o to assist you in this exploration? Or share some of the main prompts you used? Thanks!
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#96How we can have a world where this statement exists, and anyone is bullish about LLMs?
The lack of precision is appalling. I can see how a gpt-4o can be fun for toy projects, but can you really build meaningful real-world applications with this nonsense?
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#97Earlier quoted context omitted.
I've heard that many of the jobs posted on general jobs boards like that are never intended to result in a hire. They are posted when the company already knows who they are going to hire, but are legally obligated to post the position, or when the company wants to manufacture evidence that "no qualified candidates" could be found locally.
I’ve never heard of this outside of government contracts that require n+X. Is this a visa related workaround or what? Or is it just chatter from the grapevine?
If they don't suck, the guy fails the labor certification and may have to wait a year to apply for the green card again. However, he doesn't lose his job, and the qualified candidate never gets an interview.
So yes, it's pretty standard for the companies to post openings they don't have.
But I really doubt they post on the HN jobs board. Most will go through more formal channels.
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#98I wonder how this would compare against a random sample of jobs on, say, Indeed or LinkedIn. My experience of Hacker News is that it’s a very biased group (in a good way) to the general industry.
I've heard that many of the jobs posted on general jobs boards like that are never intended to result in a hire. They are posted when the company already knows who they are going to hire, but are legally obligated to post the position, or when the company wants to manufacture evidence that "no qualified candidates" could be found locally.
The HN job board is much more likely to produce a qualified candidate.
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#99> HAS TO BE A BOOLEAN VALUE! How we can have a world where this statement exists, and anyone is bullish about LLMs? The lack of precision is appalling. I can see how a gpt-4o can be fun for toy projects, but can you really build meaningful real-world applications with this nonsense?
Re: Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
#100Anyway, I have a tangential question, and this is the first time I see langchain, so may be a stupid one. The point is the vendor-API seems to be far less uniform than what I'd expect from a framework like this. I'm wondering, why cannot[0] this be done with Ollama? Isn't it ultimately just system prompt, user input and a few additional params like temperature all these APIs require as an input? I'm a bit lost in this chain of wrappers around other wrappers, especially when we are talking about services that host many models themselves (like together.xyz), and I don't even fully get the role langchain plays here. I mean, in the end, all that any of these models does is just repeatedly guessing the next token, isn't it? So there may be a difference on the very low-level, there my be some difference on a high level (considering different ways these models have been trained? I have no idea), but on some "mid-level" isn't all of this utlimately just the same thing? Why are these wrappers so diverse and so complicated then?
Is there some more novice-friendly tutorial explaining these concepts?
[0] https://python.langchain.com/v0.2/docs/integrations/chat/