What's More Likely by 2035: AI Creates New Careers or Eliminates Existing Ones?
submitted by /u/WrongdoerRough4712 [link] [留言]
找到 1418 篇相关文章
submitted by /u/WrongdoerRough4712 [link] [留言]
DIYer and TikTok user Annike Tan, who goes by @ubeboobey, can carry her cyberdeck around without anyone noticing because it doesn't look like a computer at all. Tan, who has been featured in The Cut and Wired, went viral earlier this year with a mermaid-themed cyberdeck she made inside an old purse. She has since […]
Hi, everyone I am working as a Software engineer. The past few years I oversleep a little bit in scope of AI mostly because I am sceptical about it. I decided that I would like to move on and be more up to date with it and potential use of it. How do you use it in day to day habits or work? How to monetize it? submitted by /u/Blvckhype [link] [留言]
Musk can't be trusted to protect X user privacy, public commenters warn FTC.
Meta may have found one way to slash its massive data center bill: tents.
For those doing heavy AI programming or running local models on mobile hardware: Is the current generation of iPhone Pro or Samsung Galaxy Ultra actually making a difference in your workflow, or is it mostly a gimmick right now? submitted by /u/Spirited_Good9789 [link] [留言]
On Uncanny Valley, we dive into the IPO bonanza that the top AI companies are embarking on to the point where some real estate listings are looking for not just regular old cash, but Anthropic stock.
We've poured hundreds of billions into bigger models, bigger clusters, bigger training runs, all pointed at AGI. And yet: the model still rebuilds context every few turns, still forgets what you told it ten messages ago, still degrades over long horizons. The capability is staggering and the continuity is brittle. We keep making the pattern-matcher bigger and acting surprised when a bigger pattern-matcher is still a pattern-matcher. Start with the measurement problem, because it sets up everything else. Faster output and better output are not the same thing. The industry measures speed. Tokens per second, FLOPs, parameters, because speed is easy to measure. But *effective* output, the useful work you actually get before the model starts reconstructing or fabricating what it already knew, is a different axis entirely. And on that axis, raw hardware speed tells you almost nothing. A system that generates twice as fast but burns half its output re-establishing context it should have retained isn't ahead. We've been optimizing the number that's easy to read instead of the one that matters. Here's the part I think gets skipped entirely. Current systems have no intrinsic drive. They don't want anything. They sit idle until prompted and optimize the next token. A bacterium has more impetus than a frontier model, it has a goal (find food, avoid toxin) and acts on it unprompted. That's not intelligence, it's drive, and drive is the thing evolution built *first*, hundreds of millions of years before cognition. We built the cortex and skipped the brainstem. So the bet that "scale the transformer until AGI falls out" may be optimizing the wrong layer entirely. You can't scale your way into goal-generation if goal-generation isn't a function of scale. If genuine intelligence needs a motivational substrate, something that forms its own goals and acts on them, then no cluster on earth produces it by getting larger, because it's an architecture problem, not a compute problem. That
Hey all. Been vibe coding for almost 2 years now (I think?). Previously was more focused on traditional micro-saas but recently decided to go in a different direction and see how far I could push lovable and try and make a commercial grade browser based game. Built it with Lovable + Supabase + Stripe -- full commercial browser game, gyroscope controls on mobile, no app store needed. Generated all my assets (I know, I know, there aren't a ton) with a combination of Gemini to prototype and the GPT 2 to finalize. I've made a few small games here and there that generally only get used by my kiddos, but with this one I wanted to try and create a full gaming experience (login rewards, leaderboard, store, powerup mechanics, simulated ads, etc.) Put a $100 bounty on it for the first player to reach level 100 on mobile. Nobody has claimed it since launch. So genuinely asking -- is it too hard, or is that the point? tiltra.io P.S. It is currently playable on both desktop and mobile but with the gyro mechanic it is definitely more fun and challenging on mobile. submitted by /u/BeltwayBro [link] [留言]
Scientists in Finland found bees could solve an insect version of the classic "box-and-banana" problem.
Opus 4.6 or sonnet 4.6 for rping Currently running on pro right now Im unsure what to choose between the two in terms of rping cause i prefer creative writing, stay in character, deep emotional prose, good character development, good memory, good character emotionals and stuff like that So far im using opus 4.6 but it drains the limits relatively quick For the sonnet i can use for hours and still be fine So like im wondering which is better for rping? I havent tested both deeply Also if they're an even better option, pls tell me. submitted by /u/Turbulent_Arrival_55 [link] [留言]
Gartner updated their 2026 forecast to $2.5 trillion in global AI spending. Same week, MIT's NANDA Initiative dropped a follow-up: 95% of enterprise gen AI projects deliver zero measurable return. Not low return. Zero. I've been on the delivery side of 14 of these projects since January. The MIT number doesn't surprise me. If anything it's generous. 1. 73% of the engineering work that gets AI into production has nothing to do with the model. Data pipelines, integration layers, legacy system remediation, human-in-the-loop tooling. That's where the hours go. The model is 27% of the work but gets 70%+ of the budget. Every time. 2. The budget ratio between projects that ship and projects that stall is almost exactly inverted. We tracked this through ticket history and commit logs across 14 engagements. Projects that made it to production: roughly 30% model, 70% infrastructure. Projects that stalled: 70% model, 30% infrastructure. Most companies think they're at 50/50. They're not even close. 3. One client went from 71% Copilot adoption to 34% in six months. Two other AI platform licenses dropped under 12%. Combined licensing: $340K/year. The tools worked fine. Nobody redesigned workflows to actually use them. 4. The median data error rate across our engagements is 14%. Teams always guess 5-10%. One client found 23% in month four of a $310K build. That's two months of an ML engineer building training pipelines against garbage data. $36K in salary discovering a problem a data audit would have caught in a week. 5. Medtech company. Four concurrent AI pilots. No kill criteria. $920K in engineer salary. Eleven months. Shipped: nothing. I've now seen this at six companies now. Nobody defines when to stop spending. So nobody stops. 6. Individual gains are real. Company-level ROI stays flat. HCLTech and Writer both found this from different angles. Only 29% of companies see significant ROI from gen AI, despite people at their desks reporting productivity jumps as high as 5x. I m
I have been researching how startups and developers manage AI spending across OpenAI, Claude, Gemini and other models. Many people seem to rely on spreadsheets, rough estimates or provider dashboards. I'm curious: How are you tracking AI costs today? What is the biggest frustration in your workflow? Trying to understand the problem space better before building additional features. submitted by /u/OneDisastrous7969 [link] [留言]
Code reviewed by WIRED uncovered an unreleased face-recognition system embedded in Meta’s smart glasses platform. It’s designed to identify people via biometric data stored on users’ phones.
Meta's board cites "due process" concerns over account bans. It's also pushing Meta to offer clear information about violations and its use in AI in making its determinations.
so gemma 4 dropped and my feed is three versions of the same post. "ran it last night, the local game just changed". "the cloud narrative is dying". and i caught myself getting excited and downloading it at 1am like i did for the last one. and the one before that. heres the thing thats been bugging me. i went back and looked at my own saved posts from like 8 months ago. same exact words. "this finally replaces X". "cant believe this runs on my laptop". "were so back". different model name, copy paste emotion. and almost none of those models are in my actual rotation now. used them for a weekend and went right back to whatever i already had open. i think the release is the dopamine, not the model. the download IS the fun part. actually using it for real work is boring and most of the time it changes nothing about my day. i still do the same tasks the same way. the model got better on paper and my life is identical. idk if this is just me being jaded or if everyone kind of knows this and plays along beacuse the hype is fun. im not even mad at it honestly. its just wierd to notice youve been stuck in a loop. the "everything changed" never actually changes the tuesday after. anyway gemma 4 is probably great. i downloaded it. i will use it twice. see you all next month for the same thread with a diffrent number on it submitted by /u/Napster3301 [link] [留言]
Creators often have to parse through charts and dashboards to understand their performance, but with the new AI assistant, they can get quick answers to questions like "When should I post?" and "What are people saying in my comments?"
“I think the team has really experienced the loss of a loved one with the end of the mission.”
Pretty wild case report: AI + microfluidics helped find just two viable sperm cells, and that was enough to start a pregnancy. Obviously it’s early and based on one case, but this feels like one of those “future of medicine” moments. submitted by /u/tc0843 [link] [留言]
okay so I’ve been thinking about this for a while and finally wrote it out properly everyone’s still arguing about benchmarks and which model is smarter but like… that’s starting to feel like the wrong fight? the more interesting question is where the model actually runs. on your device, in a cloud DC, on some edge hardware, inside enterprise infrastructure. that placement question is quietly becoming more important than the model quality question a few things that got me thinking about this recently: microsoft’s project solara is not a laptop. it’s basically a concept for hardware built around agents from the ground up, and they’re reportedly doing it on android not windows which says a lot about what they think “agent-native” actually needs to look like nvidia pushing local inference via RTX spark is interesting because it basically challenges the assumption that anything serious has to live in the cloud. latency, privacy, enterprise control requirements, there are real reasons to want compute closer to the user bytedance apparently building custom CPUs is the one that really made me stop. because agentic workloads aren’t just GPU jobs. agents call tools, manage state, orchestrate steps, interact with software systems. that’s a different workload profile entirely and big companies are starting to customize silicon around it anyway I wrote the whole thing up for towards AI if anyone wants to read it. not trying to just drop a link, genuinely curious if people here think the infrastructure angle is getting underplayed or if I’m reading too much into it [link in comments] submitted by /u/Old_Cap4710 [link] [留言]