Take the Developer Tools Benchmarking 2016 survey and have a chance to win some prizes

Microsoft announced today in a blog post on the Windows blog that it will sponsor the the 11th edition of the VisionMobile Developer Economics survey, a developer survey currently supported by 100+ leading developer brands and communities. If you’re a developer, the survey will take you around 15 minutes to complete and will include questions on topics such as the programming languages and tools you use, the customers you’re targeting, product features, and more. Furthermore, all participants will be able to win cool prizes including smartphones, tablets, Windows IoT dev kits, passes for developer conferences and more. Please find more details below:

The 11th edition Developer Economics survey is made by developers, for developers. Your quest is to take this survey and tell us what’s fantastic or frustrating about the tools you’re using, let us know what you’re building, why, and where you go to find out how. This survey is open to everyone involved in software development, across mobile, IoT, desktop, cloud, gaming, augmented/virtual reality, machine learning, and more!

Every participant gets something. Upon completing the survey, you’ll get access to the Developer Scorecards, helping you find out how your answers compare to other developers’ in your country, across 9+ metrics (developer experience, preferred platforms and languages, and many more). Also! We’ll be sharing the key findings of the survey in the form of the FREE State of the Developer Nation report (due July).

These are all the prizes you can win.

These are all the prizes you can win.

 

You can start the survey right here and prize drawings will happen in June. Last, you can also check the VisionMobile March Developer Economics report over here before the availability of the free State of the Developer Nation report in July 2016. If you’re a developer, will you take this survey and share your thoughts with the developer community? Let us know in the comments below.

Share This
Further reading: ,