For junior developers reading this: frameworks introduce additional complexity (especially ones with obscure dependency injection), learn how to use different t

For junior developers reading this: frameworks introduce additional complexity (especially ones with obscure dependency injection), learn how to use different tools properly and analyze when they should/should not be used. Learning your language properly (and carefully selecting when a framework makes sense vs when it doesn't) will save you much time and stress when shipping real products. There's a time and place for framework/no framework, though I'd err on the side of not introducing a huge framework until it's actually needed. Source: I work on a real, shipped for 3 years, SaaS product primarily written in Go (multiple services). The primary applications are framework-less, but some of our operators make use of kubebuilder (which certainly would qualify as a framework).