_content/blog: announce 2026 Go Developer Survey Change-Id: I6ecaef9de9659046aecea95c7f79495e34342de4 Reviewed-on: https://go-review.googlesource.com/c/website/+/851766 Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> Auto-Submit: Hyang-Ah Hana Kim <hyangah@gmail.com> Reviewed-by: Katrielle Veslenio <kveslenio@google.com> LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
diff --git a/_content/blog/survey2026-announce.md b/_content/blog/survey2026-announce.md new file mode 100644 index 0000000..89eb88b --- /dev/null +++ b/_content/blog/survey2026-announce.md
@@ -0,0 +1,21 @@ +--- +title: Help set Go's priorities for next year +date: 2026-10-21 +by: +- Cameron Balahan, on behalf of the Go team +tags: +- survey +- community +- research +summary: Share your experience with Go in the 2026 Go Developer Survey, open through November 3. +--- + +Hi Gophers! The [2026 Go Developer Survey](https://blink.qualtrics.com/jfe/form/SV_ba8fa1ZcSQQdTRs?s=b) is now open. We run this survey every year to understand how you use Go and the challenges you face. Your answers directly shape how we plan and prioritize our work. + +Last year, 5,379 of you responded, and your top frustration was making sure your code follows best practices and Go idioms (33% of respondents). Since then, we shipped a [rewritten `go fix`](/blog/gofix) in Go 1.26 that automatically modernizes your code, and added more modernizers in Go 1.27. You can read everything we learned in the [2025 results](/blog/survey2025). + +[Take the survey here](https://blink.qualtrics.com/jfe/form/SV_ba8fa1ZcSQQdTRs?s=b). It's open through **November 3**, takes about 10–20 minutes, and every question is optional. We'll share the results on this blog in early 2027. + +Please share the survey with your colleagues, friends, and online communities—the more Go developers we hear from, the better we understand what you need. + +Thank you for helping shape the future of Go!