Avoiding module mocks, building better interfaces, and preventing surprises while testing are crucial for creating effective and maintainable tests. This post highlights the downsides of excessive mocking of internal modules, and the benefits of testing through public interfaces. By following these principles, developers can reduce the risk of unexpected issues, and ensure that their tests remain relevant over time.
Jump between your projects or companies repositories with ease using FZF and Vim.
Implement Tmux-like window zoom in Vim in a couple lines of pure VimL.
