Skyrims Technologies

If you’re learning: - AI - Vibe coding - Content creation - AI automations - Building in public - SaaS Let’s connect @hkniyi🤝

This is going to be the way forward. In coming years, AI will be so good that it will be able to produce Apps and solve all kinds of problems for people easily. It will be able to produce mini apps that a user can use for specific tasks. Custom softwares and apps will be generated on the fly. I know this because I am working on something that will make all these even more easier for AI. The coming years will change everything around us.

The cycle of coding: Strong engineers built C. C inspired Python. Python built AI. AI built vibe coding. Vibe coding builds weak engineers. Weak engineers build broken systems. Broken systems force strong engineers to rise again. The cycle continues.

@svpino You are overhyped.

clawdbot is overhyped

@Ryanair @elonmusk Did you actually typed "Twitshit"?

.@elonmusk

@burkov Simplicity and minimalist design always win.

Ever wondered why modern business websites look the same? Not being an expert, I thought it's fashion, but these clowns called modern Product/UX Designers just copy these templates from the same couple of websites. If there's one profession I don't regret seeing go, it's this one. When I started to build websites, somewhere around 1998, all sites were unique. It took imagination to invent a design for a new website, and designers applied soul to their job. Twenty-five years later, they are paid for using Figma to stack prebuilt Tailwind Lego blocks. 🤮

This came as a total surprise this morning. Very humbled… 🙏 AI is built by generations of technologists, starting with the daring question of “can machines think?” by Alan Turing. It will be further developed, used and governed by many and all of us! Let’s keep our AI mission human-centered for the benefit of humanity! And I can’t wait to see where AI’s next frontier - spatial intelligence - will be taking us!

Code Red! Code Red! Attention! We have no moat! I repeat: We have no moat! This is not a drill. Code Red! Code Red!

Because of open-source, software has lost a large fraction of its perceived value. If many people needed something, there was an open-source software for this. Making business purely on software has become nearly impossible, unless you are corrupt or a monopoly. Because of LLMs, most kinds of software have lost 100% of value, because virtually anyone can get some code that does something simple you need right now, like process a data file, edit an image, or play a game. The value remains only in the ecosystem. If your software comes with an ecosystem, either an ecosystem of pieces of software, data, or users, it still has value. If it's a standalone product, everyone will assume that you've "built" it by submitting a single prompt to an LLM, because "I've built this 3D game myself with a single prompt."

Kimi K2 Thinking is here! Scale up reasoning with more thinking tokens and tool-call steps. Now live on kimi.com, the Kimi app, and API.

@soumithchintala Wishing you the very best in your next endeavor

Leaving Meta and PyTorch soumith.ch/blog/2025-11-0…

Leaving Meta and PyTorch I'm stepping down from PyTorch and leaving Meta on November 17th. tl;dr: Didn't want to be doing PyTorch forever, seemed like the perfect time to transition right after I got back from a long leave and the project built itself around me. Eleven years at Meta. Nearly all my professional life. Making many friends for life. Almost eight years leading PyTorch, taking it from nothing to 90%+ adoption in AI. Walking away from this was one of the hardest things I've ever done. But I'm leaving with a full heart. PyTorch handles exascale training now. It powers foundation models that are redefining intelligence. It's in production at virtually every major AI company. It's taught in classrooms from MIT to rural India. The tools I dreamed about making accessible? They are. The barrier to entry I wanted to lower? It's almost gone. To be clear, there’s so much more to do. As long as AI evolves at a breakneck pace, PyTorch will continue to play catch up. Obsessing over the yet-to-come sometimes makes us forget how much we’ve already done. To everyone who built this with me—who believed research should be joyful, that tools should be elegant, that open source changes everything—thank you. This wasn't my journey. It was ours. What's next for me? Something small. Something new. Something I don't fully understand yet. Something uncomfortable. I could have moved to something else inside Meta. But I needed to know what's out there. I needed to do something small again. I couldn't live with the counterfactual regret of never trying something outside Meta. It's very hard to leave. I probably have one of the AI industry’s most leveraged seats, I lead the software layer that powers the entire AI industry. Every major AI company and hardware vendor are on a speed dial. This kind of power is really hard to give up. But curiosity ultimately won out in my head. Keep making AI delicious and accessible. I'll be watching. Probably filing issues. Definitely staying involved. Is PyTorch going to be okay? I don't want to be doing PyTorch forever. I don't want to be like Guido or Linus— bound to a single thing for decades. Last November, coinciding with the birth of my daughter, I started planning my exit with Aparna. My goal was to leave PyTorch in a good and stable place. By this August, during the second half of my parental leave, I knew: Edward, Suo, Alban, Greg, John, Joe and Jana were ready. The team faced hard people, product, technical and organizational problems and didn’t feel the need to lean back on me to solve these for them (unlike in the past). The product story they crafted for the PyTorch Conference was coherent—really coherent. The things I'd flagged red were turning healthy. The project didn't need me anymore. Unlike 2020-2022 (when I stepped down to go do robotics and came back when Lin, Dima and Dwarak left), I have strong confidence that this time PyTorch is truly resilient. The most aligned culture carriers of PyTorch – Greg, Alban, Ed, Jason and Joe are at the decision table now, and people with strong value alignment – Suo, John and Jana have joined them at the table. And there’s a long list of equally value-aligned people willing to sit at the table should any of these people leave. There are many little things that make up my confidence on the people – John worked on Julia and open-source for a very long time (in fact we hacked a Torch.jl in 2015), Suo has been the strongest systems builder and strategic partner I’ve had for the past two years, and Jana worked on resilient core systems for a very long time, I’ve had long technical and organizational discussions with her over the past few months that give me confidence. And the product lineup and execution in 2025 should be sufficient evidence for any remaining doubt. I’m confident that this band of PyTorchers are going to do exceptionally well. PyTorch might change in flavor because I no longer impose my own taste from the top, but I’m confident that the values are going to stay intact and the product is going to be awesome. My time at Meta The early years of FAIR were absolutely magical. I was part of a small family of absolutely brilliant people building state-of-the-art AI out in the open. From working on GANs with Emily Denton, Rob Fergus, Leon Bottou, Martin Arjovsky and the (now legendary) Alec Radford to building Starcraft bots with Gabriel Synnaeve, to building the first FAIR Cluster with Howard Mansell, to working on object detection with Adam Lerer and Piotr Dollar, to building PyTorch. It was more fun than I can describe in words. 2015 and 2016 were probably the most productive and professionally enjoyable years of my life. I’ll probably romanticize this period of my life forever. When I joined FAIR, I had massive impostor syndrome, and the first 3 months were very very difficult. I can’t credit Andrew Tulloch enough for being the most thoughtful, kind and welcoming mentor, without whom I wouldn’t have made it. I’m so damn bullish for Meta just from the fact that he’s back. --- My time on PyTorch was special. I loved every part of building it—designing it, managing it, being the PM, TL, comms lead, doc engineer, release engineer, squashing bugs, growth hacking, turning it into a coherent product with hundreds of people, transitioning it to industry stakeholdership – the whole nine yards. To the core PyTorch team at Meta: the engineers, researchers, open-source maintainers, docs writers, CI infrastructure folks, hardware partners, the community builders. To the hundreds more inside and outside Meta—thank you. You turned a library into a movement. There are too many people to credit and thank, but I can't not mention Adam Paszke, Sam Gross, Greg Chanan, Joe Spisak, Alban Desmaison, Edward Yang, Richard Zou, Tongzhou Wang, Francisco Massa, Luca Antiga, Andreas Köpf, Zach DeVito, Zeming Lin, Adam Lerer, Howard Mansell and Natalia Gimelshein. And Schrep. They made the launch happen. And so many more people became centrally important later: Lu Fang, Xiaodong Wang, Junjie Bai, Nikita Shulga, Horace He, Mark Saroufim, Jason Ansel, Dmytro Dzhulgakov, Yangqing Jia, Geeta Chauhan, Will Constable, Briah Hirsh, Jane Xu, Mario Lezcano, Piotr Balecki, Yinghai Lu, Less Wright, Andrew Tulloch, Bruce Lin, Woo Kim, Helen Suk, Chris Gottbrath, Peng Wu, Joe Isaacson, Eli Uriegas, Tristan Rice, Yanan Cao, Elias Ellison, Animesh Jain, Peter Noordhuis, Tianyu Liu, Yifu Wang, Lin Qiao and hundreds more. It’s criminal of me to not take the space to list out everyone else I should be mentioning here. PyTorch is nothing without its people ❤️. The most joyful moments of building PyTorch was meeting users eager to share their happiness, love and feedback. I remember a grad student coming to me at Neurips 2017, in a slurring emotional voice he said he’d been trying to make progress on his research for 3 years but within 3 months of using PyTorch he made so much progress that he was ready to graduate. That moment made it tangible that what we do matters, a lot, to a lot of people, even if you don't constantly hear from them. I do miss the intimacy of the PyTorch community, with a 300 person conference that felt like an extended family gathering, but I feel that’s a small price to pay considering the scale of impact PyTorch is truly having today – yes the Conference is now 3,000 people where market-moving deals get brokered, but it’s helping orders of magnitude more people to do their best AI work. I miss the intimacy, but I'm proud of that growth. --- To Mark Zuckerberg and Mike Schroepfer, who believed that open-sourcing is fundamentally important and is a sound business strategy. This is so hard to understand for most people within the course of business, but we’ve run lock-step on this strategy without ever having to discuss it. Without you two, neither FAIR nor PyTorch would’ve happened. And those mean so much to me. To Yann LeCun and Rob Fergus, for building the magical early FAIR that I so revere. To Aparna Ramani, a leader that I find so rare at Meta in her ability to hold a really high bar for the org, technically brilliant with the span to discuss deep infra systems and industry-strategy within the same conversation and for being an absolute execution-machine! I’ve learned so much from you. To Santosh, Kaushik, Delia, Oldham and Ben for being so welcoming to Infra. For someone coming over from FAIR with a wildly different culture, you all made me feel at home and made me part of the family, and thank you for that. To all my managers who've championed me through the PSC video game – Serkan, Howard, Jerome, Abhijit, Yoram, Joelle, Aparna and Damien – I owe you a lifetime of drinks. --- Signing off for now. —Soumith

Today, we're releasing Kimi K2 Thinking, our best open-source model. What makes it different isn't just the benchmarks, though it achieves SOTA results on Humanity's Last Exam, BrowseComp, and other challenging tests. What matters is how it thinks. It reminds me of the minds on our team: always asking the next question, refusing to settle for the first answer, following each thread until it leads somewhere true. This is test-time scaling in its full form, giving models the space to think longer and act more deliberately.

China saved opensource LLMs and not only that, it made the FRONTIER opensource between July 16th and today, these are the major releases: > Kimi-K2-Thinking (1T-A32B) > MiniMax M2 > DeepSeek V3.2 > GLM-4.6 (335B-A32B) > Qwen3-VL-30B-A3B (Instruct & Thinking) > Qwen3-VL-235B-A22B (Instruct & Thinking) > Qwen3-Next 80B-A3B (Instruct & Thinking) > GLM-4.5V (VLM, 106B-A12B) > DeepSeek V3.1 > Doubao 1.6-Vision (multimodal, tool-calling) > Doubao Translation 1.5 (ByteDance, 28 Languages) > ERNIE X1.1 (Baidu, Reasoning) > Hunyuan-MT-7B & Chimera-7B (Tencent Translation Specialists) > MiniCPM-V 4.5 (8B), Tiny but GPT-4o-level VLM > InternVL 3.5 (MASSIVE Multimodal Family of Models, 1B to 241B Sizes) > Step-3 (VLM, 321B/38B) > SenseNova V6.5 (SenseTime, Multimodal) > GLM-4.5 Air (Base & Instruct, 106B-A12B) > GLM-4.5 (Base & Instruct, 335B-A32B) > Qwen 3-Coder-30B-A3B (Instruct & Thinking) > Qwen3-Coder-480B-A35B (Instruct & Thinking) > Qwen3-30B-A3B-2507 (Instruct & Thinking) > Qwen3-235B-A22B-2507 (Instruct & Thinking) > Kimi K2 (1T-A32B) US & EU need to do better

@burkov What evidence do you have to support this claim?

I'm really sorry for Richard Stallman, who wrote almost all of what everyone is now calling Linux, but it's the guy who shamelessly called a small piece of it after his name who has gotten all the credit.

@SecurityTrybe Windows NT

Which OS was your first?

We’re back! Ready to help you learn, build, and grow with technology.

Today, we announced that we plan to expand our use of Google TPUs, securing approximately one million TPUs and more than a gigawatt of capacity in 2026.

@bakwasbandkrein Moron

I'm pregnant and looking for a baby boy name that ends with “on” Help me out before my husband suggests Dragon again 🙂

Claude Desktop is now generally available. New on Mac: Capture screenshots, click windows to share context, and press Caps Lock to talk to Claude aloud.

Software development has never been about writing code. This was obvious to many before, but now AI has made it crystal clear to everyone. Building software is 99% thinking, 1% writing code, and 1% fighting off-by-1 errors.