A sad story on top of HN today - the surge of AI generated PRs means Ladybird will no longer accept PRs. AI is changing how OSS projects approach collaboration
https://t.co/GXrLJtuch6
"A substantial patch used to imply substantial effort, and that effort was a reasonable proxy for good faith. That assumption no longer holds."
Agent labs like @cursor_ai and @cognition are in a great position - they have proprietary data and are capable of post-training their own model on top of open models.
It's starting.
The company with the cheapest coding model at a good enough quality is set to win big, as devs + companies become more price sensitive.
Of all the major players, Cursor is in a v good position with their Composer model. Plus eg Factory with smart routing
the importance of understanding that being busy doesn’t mean being productive
“Sometimes the highest leverage move is to stop orchestrating entirely, close the laptop full of agents and just think hard about one single problem”
i have seen enough proof now that using a coding agent is a deep skill
it's confusing because the people you see heavily using them produce horrible results
but that's because it's a skill! you can get better and the ceiling seems pretty high - this is very exciting to me
Has been a while since I wrote about agentic engineering, so this time around some learnings of maintaining Pi as a junior maintainer to @badlogicgames :) https://t.co/TbD9Jvqk3t
@PawelJLisowski@GergelyOrosz@badlogicgames@mitsuhiko You can prompt it to do so. Or you can set up autoresearch ala Kaparthy. For me personally, it means creating my own personal projects with plugin points and hooks so that others can build their own plugins without having to modify the core.
big takeaway from @badlogicgames and @mitsuhiko interview with @GergelyOrosz is that, just like you can ask Pi to extend itself, self-improving software is a paradigm worth following
thinking about how you can build primitives so agents can mutate projects without having to fork the repo
https://t.co/OlwnTGWiXE
@m_chirculescu btw, please do let me know if I understood your question. you may have been asking about Codex internals, in which case please DM me and I can answer there
People often ask what my biggest tip is for getting the most out of Claude Code.
These days my #1 tip is: use auto mode
Auto mode means no more permission prompts. It is the key building block for multi-clauding: start a session, then while it runs, work on another session in parallel.
best thing I read this week: https://t.co/ZH392WRnKC
"If there’s an organizational mandate to leverage LLMs to minimize the time spent coding, then that’s a new constraint we can work with. We can figure out what good engineering looks like in that context. [...] It’s fundamental to understand, though, that this is not an individual’s or team’s call: it has to be an organizational decision"
to best answer this question, I built a short doc page: https://t.co/dA1UcyhDe6
tl;dr - you can build a nah preset and set policies to either allow or block (no ask). codex agents launched with this preset will run unsupervized and won't stop to ask, and dangerous actions are blocked