Yeah, as someone whose favorite file manager is Dolphin, I have the opposite preferences of the author of the marketing post. I feel like Finder is overly-simplified and tries to abstract the directory structure away from the user too much.
Self-promoting AI slop with a misleading title. No evidence that anything that controls a bridge is accessible over the internet; it’s just some PLCs accessible over the internet that may have minimal or no risk even if completely compromised.
There are probably legitimate risks but this post doesn’t provide any useful information about them.
Honestly, wouldn’t surprise me if some of these devices were honeypots, too.
What kind of bot would say `less guardrails` instead of `fewer guardrails`? I guess someone could instruct an LLM to deliberately make mistakes, but isn't that too paranoid?
15 years ago i was astounished by the intellectual deepness of this community. Now i'm aware this has always been a cult and their former cult leader Mr. Altman wants to destroy this capitalist society. He isn't even hiding motives. People just stopped listening carefully.
“include common grammatical imperfections and awkwardness common in casual message board interactions.” I’m not saying that’s what’s happening here, but a high school student told me that’s basically what they do to make papers not sound like AI.
I feel that way about a lot of very long instructions.
It seems that many of these projects are not benchmarked, so it's difficult to know whether there is an improvement in any circumstance, and what the cost is. Of course, a benchmark will be fuzzy, because codebases are all different, but it'd be a start.
Many of these skills, rules, "playbooks", and such are kitchensink attempts at steering the model. It augments the model to frame it's reasoning according to project rules and flows, but cannot be really trusted to adhere to it. More of a vibe guideline.
Imagine being a new GitHub user and you're trying to find the menu. Realizing that you have to click on a bunch of pancakes to get where you need to go would be pretty annoying.
I'm the hiring manager for this role, which is for an IC tech lead. Please see the full job description for details, but I'm looking for someone who is comfortable leading engineering discovery and working with Product on roadmap planning within the API payroll integrations space. The most important thing in this role will be driving your own pace and taking projects from inception to completion. A successful candidate will be good at working efficiently without many hard deadlines or micromanagement. We also want someone who has strong systems design experience and good technical leadership skills. In terms of tech stack, it's mostly Python and Typescript, including nest.js
Our interview process is pretty straightforward. There's a phone screen with our recruiter, then a culture fit/qualifying interview with my boss, a technical interview with a real-world problem (no leetcode), and finally a cross-functional team interview with myself and another engineering leader at my company. We move pretty quickly and aim to keep the process respectful of everyone's time.
Happy to answer any questions here! If you'd like to apply, please email recruiting [at] vestwell [dot] com with your resume.
Plus, email access is assumed for identity verification these days. Whether that's porting a number out from a wireless carrier or any service that has your email but not your phone number.
reply