Learning to code is not worthwhile. Learning computer science is. Return to the fundamental. Understand the systems, command the systems, don't be a dumb operator. For too long developers have constrained themselves to mastering a programming language and ecosystem. If you take a step back and understand the fundamentals, you can widen your scope to more languages and more ecosystems because the similarities exist but only the syntax differs.
Kimi K2.7 Code, an open-weight model, is now generally available as a selectable option in GitHub Copilot.
• Available on Pro, Pro+, Max plans with rollout starting in Visual Studio Code and other dev environments
https://t.co/ESduzvz7TO
Anyway, folks have been asking for more data on this so we published our internal results here: https://t.co/dhCMzAAhbC
Let me know what you think. Is this type of data interesting to you? How does this compare with your real-world use?
I recall in Sun back in the early 2000s that timezones were an oddly complex problem for some people on the US west coast to grok. Funny how certain things are constants in tech once you move away from those that know how to work async.
We’ve reached an agreement to acquire @ona_hq.
Its secure cloud execution technology will help Codex take on longer-running work, even when laptops are closed, and help more organizations deploy agents securely in production.
After closing, Ona will join OpenAI’s Codex team. https://t.co/RXoL4LSDcf
well thats a new one, signing up for a newsletter which wants to share my e-mail with one of their sponsors to be signed up to their e-mail list before I can fully subscribe. I guess its more honest than just sharing the info, but its a no from me.
One week to go to State of Open Con on the Road, Edinburgh. The perfect opportunity to learn about AI and open source from world-leading experts. @AmandaBrockUK, @adrianjhpc, @adrianmouat, Anastasia Stasenko, @sublimino, Camilla de Coverly Veale, Chaamini Mangaleswaran, Chris Plank, @clry2, Dave Buckley, @fintanr, Iain G. Mitchell KC, Jean-Baptiste Kempf, @justincormack, Juliette Denny, Keith Bergelt, Lee Fulmer, Liz Rice, Mallory Durran, Matt Jarvis, Matt Barker, @MikeMcQuaid, Nick Jones, @PaulaLKennedy, Sachiko Muto, @KimmichSal, and Tom Wilkinson.
We're also joined by the table holders: @Percona, @NatWestGroup, The National Robotarium by @HeriotWattUni, Occasio, @growthengineer, and @cybersecure_in.
See the speakers, schedule and get tickets at https://t.co/m2A74XvxB6
#opensource #AI #opensourceai #aiskills #stateofopencon #soocon26 #openuk #openhq #aiscotland #AI #aimodels #aiagents
This. The social contract of actually writing and understanding what you have written is vital.
I have read, and discounted until I talk to the owner, *so many* reports & docs recently, purporting to be from a human, that are largely generated by LLMs.
Great question.
I don't use LLMs for writing.
I use agents extensively for brainstorming, research, checking facts, handling markup, finding references, indexing data, and so on.
But I think that asking people to read LLM-generated text breaks a kind of social contract.
Great question.
I don't use LLMs for writing.
I use agents extensively for brainstorming, research, checking facts, handling markup, finding references, indexing data, and so on.
But I think that asking people to read LLM-generated text breaks a kind of social contract.
The conclusions here feel wrong to me. The two lessons I see are:
1. Don't run agents anywhere they might be able to access production environment credentials - it's on you to know which credentials those are
2. Keep tested backups that are independent from your production host
A little fun for a Monday, I watch a lot of rugby*, and like anyone following the @URCOfficial there are lots of possible permutations for the final three rounds, so I put together a little app to stick in the results you expect and see what the table might look like https://t.co/Y19AHlI5JC
Introducing RubberDuck in Copilot CLI: a new builtin subagent for cross model family escalations. Sonnet will now proactively solicit input from GPT 5.4 and vice versa.
In our most difficult benchmark subsets, this results in a massive 5% improvement in resolution rates