Live Podcast

Unpopular opinions about Go

Unpopular opinions about Go

Quick takeaways TODO Show notes TODO Introduction TODO

Learning Software Skills fast: what worked for us best in last 15 years

Learning Software Skills fast: what worked for us best in last 15 years

Quick takeaways TODO Show notes TODO Introduction TODO

Is Clean Architecture Overengineering?

Is Clean Architecture Overengineering?

Quick takeaways TODO Show notes TODO Introduction TODO

When you shouldn’t use frameworks in Go

When you shouldn’t use frameworks in Go

Quick takeaways Frameworks promise productivity but often lead to issues as projects get larger and more complex. The Go community prefers small, focused libraries over frameworks due to Go’s design philosophy influenced by Unix principles. Watch out for risks using frameworks like vendor lock-in, deprecation, and costly migrations that can take months. Explicit code is more maintainable than magic framework abstractions.

When it’s worth to write low-quality code

When it’s worth to write low-quality code

Quick Takeaways High-quality code is mainly about keeping good iteration speed over time - can you add features without breaking what works? Not all code needs to be high quality - focus your efforts on the code that’s most important, changes often, or creates the most value. The right time to refactor is after you know your product has value, but before technical debt gets too big - make small improvements bit by bit.

Series
Popular articles
Tags