Site feedback and FAQ

You have questions. We have answers.

Are you wondering about the evolution of IBM’s developer-related code, content, and community? Check out this list of frequently asked questions to learn more.

If you don’t find an answer for your site-related question, you can open an issue in IBM Developer’s Feedback Repository on GitHub. A member of the team will be happy to help.

Remember, this page and the GitHub repo are intended for IBM Developer website and initiative-related questions. They should not be used for product support queries. If you have questions about technology, programming methods, and other topics relevant to the wider developer community, check out IBM Developer Answers.

  • For the past two decades, developerWorks has established itself as a trusted and valuable developer brand. More recently, IBM Code has delighted developers as a platform for open source code available on GitHub. The new combined program, “IBM Developer,” builds on the strengths of both initiatives, advocating for developers and providing enhanced features, open source code, and information and resources to help you work smarter.

  • It hasn’t! The developerWorks brand is not being sunset; it is being merged with IBM Code, enhanced, and rebranded to “IBM Developer.” The developerWorks name has long been the standard at IBM for developer content. It features many great articles and tutorials to help developers find answers to pressing questions. IBM Code provides developer advocacy, code patterns in GitHub, tech talks, and other developer community tools, resources, and activities. The integration of developerWorks and IBM Code will increase focus on open source software and community enablement to help developers get their work done every day.

  • Our focus is on digital assets that are based on open source code and deployable to the IBM Cloud. You’ll find the following digital assets on IBM Developer:

    • Code patterns: Complete solutions based on open source code that are, in most cases, deployable to the IBM Cloud. They are also available in GitHub for developers to download, use, and adapt to their own solutions.
    • Tutorials: Complete step-by-step goal-focused learning that shows you how to complete one or more tasks or use cases. Our tutorials differ from code patterns in that they are usually for introductory education and granular technical tasks, while patterns are for more advanced, multi-branched coding tasks.
    • Articles: Written on specific topics to help developers who are looking to gain knowledge in a particular topic area or to simply get an overview of a technology.
    • Tech talks: Videos, including recordings of live demos and interviews, that developers can leverage to learn about technology areas. Videos can range in length from a few minutes to an hour depending on the topic area and the material being covered.
    • Blogs: Short reads from experts to let you know what’s happening in a particular technology area, a conference, or just about anything else going on in technology. If you’re looking for the latest happenings or opinions written by technology topic experts, our blog is the place to start.
  • The rebranding of developerWorks and IBM Code to IBM Developer is ongoing. The migration of content, especially on the local language sites (China, Japan, Brazil, SSA, Russia) will continue to roll out over the coming months.

  • Developers can expect to have full access to content that was previously provided by developerWorks and IBM Code. You’ll also have access to developer advocates around the world who are dedicated to helping you achieve your technology goals and grow your skills.

  • A lot! The benefits are many, but you’ll see an immediate impact from our digital assets, including open source code, patterns, and tutorials. You’ll be able to use them right away to complete your development tasks. We want you doing what’s most important to you: writing code and solving problems.

  • Not all. We’ve looked at the performance of developerWorks assets and identified a thousand or so that are actively being used. Those assets will migrate over to the new IBM Developer platform. But don’t worry, any content not migrated from developerWorks will still be in place and searchable.

  • Our focus will change over time, depending upon what developers are searching for and which technologies come to the fore. As we launch, you’ll find the topics for which we’ll accept new content submissions on this page:

  • To the fullest extent possible, we’ll continue our rich history of supporting these communities.

  • The developerWorks Twitter, Facebook, LinkedIn, WeChat and Weibo channels will be rebranded as “IBM Developer.” The existing IBM Code Twitter account will be sunset.

  • All developerWorks communities will move to a new IBM Community site. The developerWorks and IBM Code newsletters will be rebranded to IBM Developer. Developers will not need to subscribe again to the newsletters.

  • Yes. For all content that is not migrated to the new open source IBM Developer platform, the URLs will persist and the content can still be found through search engines, just like today. URLs for content that is migrated will automatically redirect to the new URL on IBM Developer.

  • We are still in the process of migrating thousands of pages of legacy content from developerWorks, while simultaneously improving the IBM Developer search capability. During the transition period, you should be able to find specific legacy pages using external search engines.

  • Same great content, brand new name. The developerWorks TV channel will be rebranded as the “IBM Developer Channel.” The existing IBM Code YouTube channel will become the IBM Code Archive.

  • As we transition to IBM Developer, we are working hard to consolidate all available code in IBM’s GitHub Enterprise organization. If anything moves, we will redirect and/or post clearly where you can find the content you’re looking for.

  • The developerWorks Blog will become the IBM Developer Blog and will remain a trusted, dynamic source for technology information.

  • We’re going to hold more of them! Our events give us a chance to meet and talk with you and the wider development community. There’s no impact on the quality and frequency, other than a rebranding to IBM Developer Events.

  • Local language sites will be rebranded as IBM Developer shortly after the launch of the worldwide English site. New content will be vetted through local language teams to ensure it adheres to the IBM strategy of developer-centric, technology-first content. The content will be migrated to GitHub (and the local sites will replicate the English redesign) as soon as possible.