This article is so interesting, but I can’t shake the feeling it was written by AI. The writing style has that feel for me. Maybe that shouldn’t bother me? Like, maybe the author would never have had time to write this otherwise, and I would never have learned about his experience. But I can't help wishing he'd just written about it himself. Maybe that's unreasonable--I shouldn't expect people to do extra work for fr…
I almost got hacked by a 'job interview'
321–330 of 534 posts
Re: I almost got hacked by a 'job interview'
#322You basically can't trust anything, unfortunately.
Solutions? Consider https://news.ycombinator.com/item?id=44283454
Re: I almost got hacked by a 'job interview'
#323Earlier quoted context omitted.
Next time maybe just post the base write up and the prompt? What value does the llm transformation add, other than wasting every reader's time (while saving yours)?
People are often unconfident about their own writing. But if you can feed it to a LLM and have the LLM output something that looks coherent, your writing is good enough to publish.
Re: I almost got hacked by a 'job interview'
#324Re: I almost got hacked by a 'job interview'
#325Earlier quoted context omitted.
Bad idea. Competent candidates might also disqualify you as employer right there. Plus you'll be part of normalizing hazardous behavior.
strong disagree. it's very similar to anti-phishing training/tests. also, being tagged as a company that cares that its potential new hires are not lazy programmers that just copy&paste because someone told them too would more than likely be taken as a positive not a negative.
Re: I almost got hacked by a 'job interview'
#326Earlier quoted context omitted.
I often ask for ai to give only grammar and spelling corrections, and then only a change set I apply manually. In other words the same functionality as every word processor since…y2k?
Why not just use one of those word processors, then? It seems like you'd expend less effort (unless there's an advantage of your approach that I'm missing), since the proof-reading systems built into a Word processor have a built-in queue UI with integrated accept / reject functionality that won't randomly tweak other parts of the paragraph behind your back.
Re: I almost got hacked by a 'job interview'
#327This article is so interesting, but I can’t shake the feeling it was written by AI. The writing style has that feel for me. Maybe that shouldn’t bother me? Like, maybe the author would never have had time to write this otherwise, and I would never have learned about his experience. But I can't help wishing he'd just written about it himself. Maybe that's unreasonable--I shouldn't expect people to do extra work for fr…
Re: I almost got hacked by a 'job interview'
#328Earlier quoted context omitted.
Why not just use one of those word processors, then? It seems like you'd expend less effort (unless there's an advantage of your approach that I'm missing), since the proof-reading systems built into a Word processor have a built-in queue UI with integrated accept / reject functionality that won't randomly tweak other parts of the paragraph behind your back.
Far better at catching some types of mistakes. Word only has this many hardcoded rules past the basic grammar. LLMs operate on semantics, and pick up on errors like "the sentence is grammatically correct, but uses an obviously wrong term, given the context".
Re: I almost got hacked by a 'job interview'
#329Earlier quoted context omitted.
I stopped reading a few paragraphs in. I get the point of the article. Be careful running other people's code on your machine. After understanding that, there's no point to continue to read when a human barely even touched the article.
I found the details of how the attack was constructed to be interesting.
Re: I almost got hacked by a 'job interview'
#330Earlier quoted context omitted.
> Seasoned accounts are a positive heuristic in many domains, not just LinkedIn. Yep. This is how the 3 major credit bureaus is the United States to verify your identity. Your residence history and your presences on the distributed Internet is the HARDES to fake.
sucks to be young I guess.
(Except maybe the sorts of idiots who write job descriptions requiring 10+years of experience with some tech that's only 2 years old, and the recruiters who blindly publish those job openings. "Mandatory requirements: 10+ years experience using ChatGPT. 5+ years experience deploying MCP servers.")