IfFailGo and the language feature / pattern principle
Exceptions are “just” an undeclared return value, which cascade by default.
Jay Bazuzi
Author of Unremarkable Code
Latest posts
Measuring 3PP Health
If a critcial security vulnerability is found in a library we depend on, how quickly can we find out, apply the fix, verify, and ship to production?
The one true .gitattributes
I take it as a fundamental tenet of source control systems that I can put a file in now and get it out later, unchanged. Git breaks this rule: Git can convert line endings, which which regularly causes confusion and file corruption. Let’s stop that from happening.
Hermetic Python
Suppose we have some Python that depends on some 3rd-party libraries. How do ensure that those 3rd-party dependencies are stable over time, so we can get consistent results, in accordance with good engineering practice?
Understanding minidump debugging
Programs are just data in memory Code is just data. Running programs are just data in memory. Debuggers just inspect that data. What if we take a snapshot? (Part 5 of a series on Windows debugging.)
How to make Source Server work with Git
Git doesn’t plug in easily with Source Server. How can we make it work? (Part 4 of a series on Windows debugging.)
Finding source code in Visual Studio, with Source Server
When you build your source code locally on your development machine and then run it under the debugger, the debugger finds the debugging information automatically. What about when you didn’t build the program yourself? (Part 3 of a series on Windows debugging.)
What is Debug Info? (An Explainer)
Debug Info is the information about a running program that the debugger uses to understand that program. Let’s delve… (Part 1 of a series on Windows debugging.)
How the Visual Studio Debugger Finds Debug Information
When you build your source code locally on your development machine and then run it under the debugger, the debugger finds the debugging information automatically. What about when you didn’t build it yourself? (Part 2 of a series on Windows debugging.)
When Mocks are OK
Mocks are evil. Except for the Three L’s and TDA.