{"id":4592,"date":"2026-07-16T13:05:38","date_gmt":"2026-07-16T13:05:38","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/07\/16\/the-developer-has-changed-so-should-developer-conferences\/"},"modified":"2026-07-16T13:05:38","modified_gmt":"2026-07-16T13:05:38","slug":"the-developer-has-changed-so-should-developer-conferences","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/07\/16\/the-developer-has-changed-so-should-developer-conferences\/","title":{"rendered":"The Developer Has Changed. So Should Developer Conferences"},"content":{"rendered":"

Why Docker is excited to co-host the first WeAreDevelopers World Congress North America<\/em><\/h1>\n
\n \"WAD\n <\/div>\n

When we announced our partnership with WeAreDevelopers<\/a>, AI agents were still mostly something developers experimented with. Today, they\u2019re becoming part of everyday software development.<\/p>\n

That\u2019s why the timing for this year\u2019s WeAreDevelopers World Congress couldn\u2019t be better.<\/p>\n

In the months since that announcement, the developer landscape has changed dramatically. If you\u2019re writing software today, your workflow probably looks very different than it did a year ago. You\u2019re prompting AI agents, reviewing AI-generated code, deciding what to accept and what to reject, and thinking about security much earlier in the development process.<\/p>\n

Developers are no longer spending all of their time writing code. They\u2019re designing systems that generate code, supervising autonomous agents, deciding what those agents can access, reviewing AI-generated changes, and making sure software is secure before it reaches production.\u00a0<\/p>\n

That shift feels a lot like the rise of data science a little over a decade ago. We didn\u2019t replace programmers. We created an entirely new discipline that blended software engineering, mathematics, and statistics into something bigger.<\/p>\n

I think we\u2019re seeing the beginning of a similar transformation. Whether we continue calling ourselves developers, builders, or something entirely new almost doesn\u2019t matter. The role itself is changing.\u00a0<\/p>\n

The best engineers of the next decade won\u2019t simply write software. They\u2019ll orchestrate teams of AI agents, establish the guardrails those agents operate within, and ultimately remain accountable for the systems they create.<\/p>\n

That\u2019s the conversation our industry needs to have. It\u2019s also why this year\u2019s WeAreDevelopers World Congress feels so important.<\/p>\n

A conference built around developers<\/strong><\/h3>\n

From September 23 through 25<\/strong>, thousands of developers will gather at the San Jose McEnery Convention Center<\/strong> for the first ever WeAreDevelopers World Congress North America<\/strong><\/a>.<\/p>\n

Docker is proud to serve as a presenting partner, but our goal isn\u2019t to make this a Docker event.<\/p>\n

Our goal is to help create a place where developers can learn from each other.<\/p>\n

That\u2019s why we partnered with WeAreDevelopers in the first place. They\u2019ve spent more than a decade building one of the world\u2019s strongest developer communities by focusing on the people building software, not the companies selling it. As AI reshapes how software gets built, North American developers need more than another vendor conference. They need a place to compare notes, share what\u2019s actually working, challenge assumptions, and learn from peers facing many of the same questions.<\/p>\n

The best developer conferences have never been about product launches. They\u2019re about conversations. They\u2019re about seeing how other engineers solve problems, discovering tools you didn\u2019t know existed, and leaving with ideas you can actually use on Monday morning.<\/p>\n

That\u2019s what has made WeAreDevelopers so successful around the world, and that\u2019s what we\u2019re excited to help bring to the U.S.<\/p>\n

The conversation has changed<\/strong><\/h3>\n

Over the last year, nearly every conversation I\u2019ve had with engineering leaders has landed in the same place.<\/p>\n

Everyone wants the productivity gains that AI agents promise.<\/p>\n

If you\u2019ve spent any time with Claude Code, Cursor, Codex, or another coding agent, you\u2019ve probably experienced it yourself. You can move faster than ever before. Then you stop and ask a different set of questions.<\/p>\n

What is the agent actually doing?<\/p>\n

Can it reach internal systems?<\/p>\n

What credentials is it using?<\/p>\n

Where is my data going?<\/p>\n

How much autonomy am I comfortable giving it?<\/p>\n

Those questions aren\u2019t theoretical anymore. They\u2019re becoming everyday engineering problems.<\/p>\n

At Docker, they\u2019ve shaped much of what we\u2019ve been building.<\/p>\n

We\u2019ve introduced Docker Sandboxes so developers can run AI agents safely without changing how they work. We\u2019ve launched Docker AI Governance to give organizations visibility and control over autonomous agents. We\u2019ve continued investing in Docker Hardened Images because supply chain security only becomes more important as AI generates more code.<\/p>\n

They\u2019re all pieces of the same philosophy.<\/p>\n

You shouldn\u2019t have to choose between moving fast and staying secure.<\/p>\n

The tooling should make both possible.<\/p>\n

Meet the Docker team<\/strong><\/h3>\n

We\u2019ll have Docker engineers and leaders speaking throughout the event, including:<\/p>\n