HeyJaredThe Polymathic Engineer
A newsletter about Algorithms, Computer Vision, and Distributed Systems
- Indexed issues, last 90 days
- 12
- Latest publication
- Sep 25, 2026
- Audience
- Checking…
- Earliest in this view
- Jul 11, 2026
Latest issues
The most dangerous change to a published API is a rename (opens the original)
Read excerpt
Hi Friends,Welcome to the 192nd issue of the Polymathic Engineer newsletter. This week's article continues our API design series.Last time, we focused on the core rules for creating intuitive and easy-to-evolve APIs—things like proper resource modeling, adopting standards, and reporting errors customers can build on. We wrapped up by promising to show you how to automate all of these rules: the OpenAPI Specification (OAS). The spec describes the API's layout (e.g., endpoints, authentication, par
You can refactor everything except your API (opens the original)
Read excerpt
Hi Friends,Welcome to the 191st issue of the Polymathic Engineer newsletter. This week, we are starting a new series of articles on API design.Let’s be honest: building an API is quite fast with modern frameworks. You can get a working endpoint up and running in minutes. The real nightmare starts a few months later, once consumers rely on the API. Then every name you picked and structure you chose becomes difficult to change or remove. Here, we will explore how to design APIs that are intuitive
Latency: What It Is and What Limits It (Part II) (opens the original)
Read excerpt
Hi Friends,Welcome to the 190th issue of the Polymathic Engineer newsletter. This week, we continue our series of articles on latency.At the end of Part I, we posed two open questions. If latency is a distribution, not a single number, where does all that variance come from? And how do we measure it? This issue answers both, starting with a tour of the entire stack.The outline is as follows:- Sources of latency- How latency compounds- Measuring without lying to yourself- Hands-on: measure your o
Latency Is Not a Single Number (opens the original)
Read excerpt
Hi Friends,Welcome to the 189th issue of the Polymathic Engineer newsletter. In this week’s article, we start discussing latency in depth.Latency is one of those things that every software engineer has to deal with, but few make the effort to really understand it. We all know that fast is good and slow is bad. But when we try to put some definition on what latency is, what limits it, and how to quantify it, things get a bit fuzzier. Since you can’t improve what you can’t define or measure, it’s
Exception Handling in Practice (opens the original)
Read excerpt
Hi Friends,Welcome to the 188th issue of the Polymathic Engineer newsletter.Errors and exceptions are inevitable. Every code can fail when something unexpected happens, or when it runs in an environment it wasn’t designed for. Many unexpected things can occur like running out of memory errors, and so on.That’s why handling failures should be one of the first things we think about when designing our code. However, the dangerous failures are not the ones that crash our application. They are the si
Publishing over time
Last 90 days. Choose a month to open its work.
Recurring subjects
Named in the text we hold. One piece can cover several.
Audience
No verified audience measurement yet.
About this data
Counts cover the work we have indexed. Tone needs enough text and a confident classification. Excerpts and episode notes are not full articles or transcripts.
Identity or attribution wrong? Suggest a correction.