josephwegner
This is pretty shady. The $17B figure is much less impressive when a huge chunk of it is hinged on competitors choosing to hurt their business.
The provided software is clunky, and the plugins suck. I’ve been building an app for designing stickers, and what I really want is to either be able to drive the Cameo from the app directly, or output a design file in a format that can be loaded straight into the software to start cutting.
The thing I’m stuck on is… how do people reverse engineer these devices protocols, without fear of bricking the device? My understanding is that reverse engineering like this is a lot of “try shit and see if it works”. It seems to me that a few wrong commands could get the cameo in some irrecoverable state. Obviously that’s not a risk I’m willing to take on a machine I use very regularly.
OpenAI gives first detailed debrief of the Hugging Face incident at Black Hat
Mythos model found vulnerabilities in classified US Government systems
Orion 1.1 for macOS is out, with containers
Jury clears Boeing in 737 MAX fraud lawsuit
Personal Computer by Perplexity
Show HN: Not All Agents – convince a room of agents that you're one of them
Trump announces 'major combat operation' in Iran
Waiting for dawn in search: Search index, Google rulings and impact on Kagi
The All-New Slackbot: Your Personal AI Agent for Work
- Before cell phones, we were also in an age of far less mass violence in American schools. I completely empathize with parents wanting their kids to have an emergency contact device, given the relative increase in violence at schools.
- There is a long history of kids being abused, sexually or otherwise, by authority figures in their school. Having a lifeline like a quick text to a parent can easily be the escape hatch from a predator convincing a kid to do something unsafe.
Paramount hostile bid for Warner Bros., challenging offer by Netflix
RFC: PHP license update
This doesn't seem applicable in most contexts. Yes, when I'm coding for fun or purely for learning the finished product is less relevant... but I'd guess the vast majority of code that is written is for a business that _only_ cares about the product. Code is an implementation detail.
If (and this is a _big_ if) AI-based coding can increase developer velocity even as little as 50%, no sane business is going to let their engineers ignore it just because it's not as fun as artisanal code.
It’s been a common mantra - at least in my bubble of technologists - that a good majority of the software engineering skill set is knowing how to search well. Knowing when search is the right tool, how to format a query, how to peruse the results and find the useful ones, what results indicate a bad query you should adjust… these all sort of become second nature the longer you’ve been using Search, but I also have noticed them as an obvious difference between people that are tech-adept vs not.
LLMs seems to have a very similar usability pattern. They’re not always the right tool, and are crippled by bad prompting. Even with good prompting, you need to know how to notice good results vs bad, how to cherry-pick and refine the useful bits, and have a sense for when to start over with a fresh prompt. And none of this is really _hard_ - just like Search, none of us need to go take a course on prompting - IMO folks jusr need to engage with LLMs as a non-perfect tool they are learning how to wield.
The fact that we have to learn a tool doesn’t make it a bad one. The fact that a tool doesn’t always get it 100% on the first try doesn’t make it useless. I strip a lot of screws with my screwdriver, but I don’t blame the screwdriver.
Not that that takes away from the article at all. This project has many merits, and although cost may not be one of them, it’s still interesting!