From Java to Go: I Have a Hammer and See Nails Everywhere
summary
Compares Java habits to Go and gives concrete rules: the compiler merges package files and anything under the internal folder is hidden so start small; shows a baker counter example where a pointer receiver is required because value copies don’t mutate, explains when pointers help with mutability or large structs, argues for placing implicit interfaces on the consumer side to keep APIs minimal, and replaces fragile mocking with testcontainers for reliable integration tests.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:57Java vs Go differences
- 7:09Go code and structs
- 9:14Understanding interfaces and implicit design
- 11:23Pointers and receivers
- 16:00Takeaways
