Studio Pulpit

Studio Pulpit - it's all about data. Tweets sent by Jack Esselink @esselinj

[Studio Pulpit @studiopulpit]

Interesting to read how #openai goes about its transfornation towards using #agentic workflows in coding #ai

[Greg Brockman @gdb]

Software development is undergoing a renaissance in front of our eyes.

If you haven't used the tools recently, you likely are underestimating what you're missing. Since December, there's been a step function improvement in what tools like Codex can do. Some great engineers at OpenAI yesterday told me that their job has fundamentally changed since December. Prior to then, they could use Codex for unit tests; now it writes essentially all the code and does a great deal of their operations and debugging. Not everyone has yet made that leap, but it's usually because of factors besides the capability of the model.

Every company faces the same opportunity now, and navigating it well — just like with cloud computing or the Internet — requires careful thought. This post shares how OpenAI is currently approaching retooling our teams towards agentic software development. We're still learning and iterating, but here's how we're thinking about it right now:

As a first step, by March 31st, we're aiming that:

(1) For any technical task, the tool of first resort for humans is interacting with an agent rather than using an editor or terminal.
(2) The default way humans utilize agents is explicitly evaluated as safe, but also productive enough that most workflows do not need additional permissions.

In order to get there, here's what we recommended to the team a few weeks ago:

1. Take the time to try out the tools. The tools do sell themselves — many people have had amazing experiences with 5.2 in Codex, after having churned from codex web a few months ago. But many people are also so busy they haven't had a chance to try Codex yet or got stuck thinking "is there any way it could do X" rather than just trying.
- Designate an "agents captain" for your team — the primary person responsible for thinking about how agents can be brought into the teams' workflow.
- Share experiences or questions in a few designated internal channels
- Take a day for a company-wide Codex hackathon

2. Create skills and AGENTS[.md].
- Create and maintain an AGENTS[.md] for any project you work on; update the AGENTS[.md] whenever the agent does something wrong or struggles with a task.
- Write skills for anything that you get Codex to do, and commit it to the skills directory in a shared repository

3. Inventory and make accessible any internal tools.
- Maintain a list of tools that your team relies on, and make sure someone takes point on making it agent-accessible (such as via a CLI or MCP server).

4. Structure codebases to be agent-first. With the models changing so fast, this is still somewhat untrodden ground, and will require some exploration.
- Write tests which are quick to run, and create high-quality interfaces between components.

5. Say no to slop. Managing AI generated code at scale is an emerging problem, and will require new processes and conventions to keep code quality high
- Ensure that some human is accountable for any code that gets merged. As a code reviewer, maintain at least the same bar as you would for human-written code, and make sure the author understands what they're submitting.

6. Work on basic infra. There's a lot of room for everyone to build basic infrastructure, which can be guided by internal user feedback. The core tools are getting a lot better and more usable, but there's a lot of infrastructure that currently go around the tools, such as observability, tracking not just the committed code but the agent trajectories that led to them, and central management of the tools that agents are able to use.

Overall, adopting tools like Codex is not just a technical but also a deep cultural change, with a lot of downstream implications to figure out. We encourage every manager to drive this with their team, and to think through other action items — for example, per item 5 above, what else can prevent a lot of "functionally-correct but poorly-maintainable code" from creeping into codebases.

[OpenAI @OpenAI]

Great day to be a Plus user.

[OpenAI @OpenAI]

Since the initial launch, we’ve made some improvements to deep research:

✅Embedded images with citations in the output

✅Better at understanding and referencing uploaded files

[Studio Pulpit @studiopulpit]

@SVG__Collection Kind of blue - Miles Davis

[Studio Pulpit @studiopulpit]

Lees hier het interview met Jack Esselink @esselinj van Studio Pulpit over de impact van #AI in het Insights Magazine van de @BusinessClubNV https://t.co/OBYPfsJ635

[OpenAI @OpenAI]

We're updating our data controls for ChatGPT Free and Plus users.

Now, you can access your chat history regardless of whether you’re opted into training for model improvement. If you’ve previously opted out, your choice will remain. Available on web today, and mobile soon.

[AI at Meta @AIatMeta]

Introducing Meta Llama 3: the most capable openly available LLM to date.

Today we’re releasing 8B & 70B models that deliver on new capabilities such as improved reasoning and set a new state-of-the-art for models of their sizes.

Today's release includes the first two Llama 3 models — in the coming months we expect to introduce new capabilities, longer context windows, additional model sizes and enhanced performance + the Llama 3 research paper for the community to learn from our work.

More details ➡️ https://t.co/nFll4exicO
Download Llama 3 ➡️ https://t.co/Ps0OAHt0RR

[OpenAI @OpenAI]

You can now edit DALL·E images in ChatGPT across web, iOS, and Android.

[Studio Pulpit @studiopulpit]

Ai geeft Python wind in de zeilen #ai #python #machinelearning https://t.co/hn2sAt4myM

[David J. Gunkel @David_Gunkel]

For what it's worth, @MCoeckelbergh and I agree that #ChatGPT cannot be an author, but for entirely different reasons that question rather than endorse logocentric metaphysics.
https://t.co/pZyc4yPiD0

[Studio Pulpit @studiopulpit]

@meta loves #python ! https://t.co/tnGC6sHlxc via @metaOpenSource

[AI Theoloog - Jack Esselink @aitheoloog]

Vandaag is het tweede blog van de series 'spirituele en religieuze dimensies van #AI' verschenen op @TheologieNL met als titel 'Kunstmatige intelligentie geschapen naar ons evenbeeld' en gaat over echtheid en #creativiteit. https://t.co/vmo2JOVl6T

[Studio Pulpit @studiopulpit]

What’s New in Pandas 2.2 #pandas #datascience #ai #sklearn https://t.co/bKarzitlJa

[Studio Pulpit @studiopulpit]

'#AI kan niet zonder goede #theologie' - nieuw opinieartikel van Jack Esselink @esselinj in @iBestuur https://t.co/9XuvUVyOeC #opinie #kunstmatigeintelligentie

[Yann LeCun @ylecun]

IBM & Meta are launching the AI Alliance to advance *open* & reliable AI.
The list of over 50 founding members from industry, government, and academia include AMD, Anyscale, CERN, Hugging Face, the Linux Foundation, NASA....
https://t.co/NdcMb7GMXv

[Jack Esselink @esselinj]

What is a large language model #LLM and how does it work? Great primer by @karpathy #AI #chatgpt
https://t.co/8TZxz4tc8D

[Carissa Véliz @CarissaVeliz]

I've heard experts say that #LLMs learn a lot about the world in the process of statistically predicting what the next word is. I think that's wrong. If they "learn" anything at all, they learn about how humans use language—not about the world. The distinction matters. #AIEthics

[Studio Pulpit @studiopulpit]

LlamaIndex: Augment your LLM Applications with Custom Data Easily - https://t.co/d9TpY5GXtq #genAI #AI #LLM https://t.co/ug917J2ifd

[Jeremy Howard @jeremyphoward]

Here, in full directly on Twitter, is "A Hackers' Guide to Language Models". This 90 minute tutorial is designed to be the one place I point coders at when they ask "hey, tell me everything I need to know about LLMs!"

It covers both @OpenAI models and open source ones in depth.

[Sven Nyholm @SvenNyholm]

Launching today: the brand new This is Technology Ethics podcast. My friend/collaborator @JohnDanaher & I discuss themes from my book This is Technology Ethics (@PhilosophersEye), in 9 episodes, the two first of which are available now! #technology #ethics
https://t.co/ikWqkFQHhI