Jay Conrod's Blog
Itegration tests are the most important kind of tests. You should strive for excellent integration test coverage and invest relatively little time in unit tests. I've believed this since I worked on cmd/go, Go's build tool. We had a really excellent set of integration tests that were easy to write,
- Posts
- 99 from 1 Jan 2008 to 29 Oct 2026
- Posting
- now and then (3 in the last year)
- Kind
- personal blog
- Feed
- https://jayconrod.com/feed
2026 3
2025 2
2023 4
2022 3
2021 2
2020 5
2019 2
2018 4
2017 8
2016 9
2015 9
2014 10
- Gypsum now has type parameters!
- Structure of the Gypsum compiler (part 3)
- Structure of the Gypsum compiler (part 2)
- Structure of the Gypsum compiler (part 1)
- Introducing Gypsum
- Pinky and the god: Avoiding Emacs-induced RSI
- Emacs: Run git-blame on the current line
- The Strahler number
- How to build a parser by hand
- New and improved blog software
2013 3
2012 5
2011 8
- A tale of two benchmarks
- Polymorphic Inline Caches explained
- How to use Emacs like GNU Screen
- A brief explanation of Scala 2.8 collections
- A simple interpreter from scratch in Python (part 4)
- A simple interpreter from scratch in Python (part 3)
- A simple interpreter from scratch in Python (part 2)
- A simple interpreter from scratch in Python (part 1)
2010 6
2009 9
- Tutorial: Reverse debugging with GDB 7
- Processing large files in Scala
- Midrange computers are amazingly cheap
- Scala's IDE support is terrible
- Tutorial: Function Interposition in Linux
- Demise of the BBS
- Keeping a developer diary
- How to use HTTP cookies in Python
- Currying and why we don't pass arguments as tuples