In the very general sense of design patterns - sure, you always need to design your code regardless of the language. Sometimes that's called design principles (

In the very general sense of design patterns - sure, you always need to design your code regardless of the language. Sometimes that's called design principles (https://stackoverflow.com/questions/31317141/whats-the-difference-between-design-patterns-and-design-principles https://stackoverflow.com/questions/31317141/whats-the-diffe...). If you're focusing too much on specific patterns, you might be wasting your time. For example, the O in SOLID is really only relevant for inheritance which Go doesn't have. And even when a concept is relevant to Go, it's questionable how much benefit there is to think about it explicitly. Unless you want to write books and blogposts of course.