Офер VK для бэкенд-разработчиков за выходные
VK проводит Weekend Offer для бэкенд-разработчиков. Если вы больше 3 лет пишете на Java, Go, Python или C++ — у вас есть все шансы получить приглашение на работу за 2 дня: технические собеседования 28 июня, а финалы, знакомство с командами и офер 29 июня.
Отправляйте заявку до 25 июня и станьте частью VK! Подробнее о мероприятии — на сайте.
VK проводит Weekend Offer для бэкенд-разработчиков. Если вы больше 3 лет пишете на Java, Go, Python или C++ — у вас есть все шансы получить приглашение на работу за 2 дня: технические собеседования 28 июня, а финалы, знакомство с командами и офер 29 июня.
Отправляйте заявку до 25 июня и станьте частью VK! Подробнее о мероприятии — на сайте.
Announcing GoReleaser v2.10
- New Homebrew Casks support - Replaces the old
- Easy migration - Most users just need to rename
- Experimental MCP server - Adds Model Context Protocol support for AI tools like Claude Desktop (just run
https://carlosbecker.com/posts/goreleaser-v2.10
- New Homebrew Casks support - Replaces the old
brews
section which was incorrectly using Homebrew Formulas for pre-built binaries. The new homebrew_casks
section does it properly.- Easy migration - Most users just need to rename
brews
to homebrew_casks
in their config- Experimental MCP server - Adds Model Context Protocol support for AI tools like Claude Desktop (just run
goreleaser mcp
)https://carlosbecker.com/posts/goreleaser-v2.10
Go should be more opinionated
TL;DR:
The author argues that Go should provide more opinionated guidance on application structure and project layout. While Go excels at having "one way to do things" for language features (formatting, loops, etc.), it lacks official guidance for organizing larger projects.
Key points:
- Go's simplicity makes it easy to learn, but structuring real-world projects becomes challenging
- Teams spend significant time researching and deciding on project structure
- Official templates for common patterns (CLIs, APIs, microservices) would help
- Similar to how
- Would especially benefit teams migrating from opinionated frameworks like Spring Boot or Laravel
Bottom line: Go needs official project scaffolding tools (like
https://eltonminetto.dev/en/post/2025-06-19-go-more-opinated
TL;DR:
The author argues that Go should provide more opinionated guidance on application structure and project layout. While Go excels at having "one way to do things" for language features (formatting, loops, etc.), it lacks official guidance for organizing larger projects.
Key points:
- Go's simplicity makes it easy to learn, but structuring real-world projects becomes challenging
- Teams spend significant time researching and deciding on project structure
- Official templates for common patterns (CLIs, APIs, microservices) would help
- Similar to how
go mod
solved dependency management fragmentation- Would especially benefit teams migrating from opinionated frameworks like Spring Boot or Laravel
Bottom line: Go needs official project scaffolding tools (like
go new
) to extend its opinionated philosophy beyond language syntax to application architecture.https://eltonminetto.dev/en/post/2025-06-19-go-more-opinated