Making the business case for Watson DevCon

Republished from the Watson Blog

As conference season gears up, most of us busy making plans and our shortlist for the rest of 2016. Much of that pre-planning involves securing the budget and making the business case for attendance. From actual conference cost to securing budget for travel, the road to getting sign off can be a tough one. Although often challenging, it is not impossible!

Why Watson DevCon?

We tapped some of our top Watson developers and asked them why [and how] the Watson Developer Conference moves the needle in industry knowledge and professional growth [Hint: This is the stuff to use in your Justification Letter].

Here’s an overview:

  • Work with the technology – Not so long ago Watson Developer evangelist Zach Walchuk announced the conference on our blog and explained the benefits of getting hands on time with Watson technology. What does this mean? You get access to the latest APIs AND the folks who actually built it. Have a real-time question? Hit a roadblock? Just want to chat about your latest ideas or projects? You can do all of the above at the conference. This is the time to collect the knowledge from the source and share it back with your team. Whether you are looking to build your goto-market strategy or figure out in-market applications, this is where you can get to those next steps.

Watch the video (
  • Hear from top leaders within the industry– Twilio, Slack, OmniEarth and Uber. Just a few of the industry leaders and innovators who will take the stage at the Watson Developer Conference. Learn lessons and gather insights from some of the top thinkers and creators within the cognitive space. The presentations and flash talks will supply you with actionable information about current industry perspectives, resources and a critical roadmap of where Watson is heading in the near future. Return to your team and speak confidently about the future of cognitive and AI with a firm outlook on your company’s positioning for the next wave of industry trends. In fact, you can follow our #WatsonDevCon speaker Twitter list here.

Read why Reah Miyara, IBM Watson Product Manager is going to the Watson Developer Conference and why you should, too. Finally, let’s not forget:

  • Networking – This is an obvious benefit, but one that cannot be discounted. 1,000 of the top developers, leaders and brilliant thinkers are expected to join us in San Francisco. Our bench is deep and we’re excited to share it with you. You might have noticed a few of our most talented developers and thinkers on Medium, GitHub or LinkedIn [If you haven’t you might want to check out Josh, Ashley or Michael on IBM Watson Developer Cloud]. Many of them will be there on the floor—at break out sessions, 1:1’s and flash talks. Exchange ideas, follow each other on Twitter or grab a coffee. We made the networking piece simple

Before you head to the airport

So here’s some homework to get you started. Get a complete quick hit of Watson 101 here. This will get you running and is also a solid refresher on the technology.

Other prep info:

Have a question? Send us a tweet and don’t forget to use #WatsonDevCon.

Share this post:

Share on LinkedIn

Add Comment
No Comments

Leave a Reply

Your email address will not be published.Required fields are marked *

More Events Stories

Open Data Science Innovation in the Cloud

Today IBM will share important announcements for helping customers to use Spark, R, and open data science to drive business innovations in the cloud.

DockerCon 2016: Think inside the box

On June 19th – June 21st, a massive convergence of developers, users, and industry leaders will descend on the Washington State Convention Center to talk about one of the hottest topics in tech: Containers! As the container community continues to grow, DockerCon will be a great place to hear the latest news, developments and enhancements to this technology and growing ecosystem of players.

Twilio Signal – Anyone can build code

If Day One of the Twilio Signal conference was about driving home the message that "anyone can be a developer," then Day 2 was "anyone can build code."