TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The Pragmatic Engineer published an interview with Sean Allen, a distinguished engineer at Antithesis, on software correctness and supply-chain security. Allen argues for designing systems around explicit guarantees and repeated workloads, and says there is no single or simple fix for attacks that exploit trusted software ecosystems.
The Pragmatic Engineer published an interview with Sean Allen, a distinguished engineer at Antithesis and a core contributor to the Pony programming language, about software correctness, testing and supply-chain security. Allen argues that correctness should be designed into software from the start, while warning that there is no single or simple fix for attacks that exploit trusted software dependencies.
Allen defines correctness in terms of whether a program does what its users and operators expect. He uses invariants—formal guarantees about system behavior—as a way to describe that goal. But he told interviewer Gergely Orosz that teams often do not know what they expect a system to do until it fails. In practical terms, he described software as correct enough when it serves its business purpose and does not cause an overnight outage.
The interview challenges the idea that testing alone can establish correctness. Allen argues that manual testing is a weak foundation when a language can instead make invalid states impossible to express. He also favors defining repeatable workloads to exercise software over time, rather than relying only on unit tests. One example discussed is the Bank Test, used to stress database isolation guarantees.
On development process, Allen pushes back on treating quality as a late-stage gate in a CI/CD pipeline. He favors building validation and feedback into development from the beginning. The discussion also covers technical debt, garbage collection and the Pony language’s approach to predictable performance. These are Allen’s views in an interview, not findings from a new study or an independent evaluation of the methods described.
Designing Correctness Into Software
The discussion matters to engineering teams because software failures can affect service availability and business operations, while code and dependencies are built and reused across complex systems. Allen’s emphasis on invariants and continuous feedback frames correctness as a design concern rather than a final inspection step.
His supply-chain warning also points to a difficult trade-off: software projects often depend on shared packages, but the source says popular programming languages generally assume a trustworthy ecosystem. Allen says languages with stronger defenses, such as E, have not become popular enough to offer a broad answer. The interview does not quantify the risk or compare defenses, but it highlights why dependency security cannot be reduced to a single tool or process.
Products Worth Considering
Bose QuietComfort Earbuds (2nd Gen) – True Wireless Bluetooth Earbuds with Active Noise Cancellation
LG UltraGear 32GX850A-B 32-inch 4K UHD OLED Gaming Monitor
Jackery Explorer 300 Portable Power Station with SolarSaga 100W Solar Panel
As an affiliate, we earn on qualifying purchases.
The Interview’s Engineering Focus
The article is a wide-ranging conversation rather than a report of a newly announced product, vulnerability or security incident. Orosz says he sought Allen’s perspective because of his work on confidential computing at Microsoft, his experience with Pony and his focus on software correctness at Antithesis. The interviewer also says the subject has gained attention as code-generating agents produce more code, which he sees as creating more opportunities for bugs to reach production.
The source identifies Antithesis as a sponsor of the podcast, while stating that the interview itself was not sponsored by the company. It also includes a separate announcement that The Pragmatic Summit will return Feb. 10 in San Francisco, with tickets priced at $1,000 and WorkOS as its exclusive sponsor. That event announcement is distinct from the interview’s main subject.
““It’s down to whether my program does what I expect.””
— Sean Allen, in The Pragmatic Engineer interview
Limits of the Security Advice
The source provides Allen’s assessment, not a detailed threat analysis or a comparison of specific supply-chain security products. It does not identify a particular attack, quantify how often package hijacking occurs or set out a complete mitigation plan. The discussion therefore supports the conclusion that Allen sees the problem as difficult, but not a ranking of defenses or a claim that any one language or practice resolves it.
The supplied report excerpt ends during the interview’s discussion of beautiful code, so it does not contain the full conversation. It is also unclear from the excerpt how Allen’s workload approach is implemented in practice, what results it has produced, or how broadly his views are shared across engineering teams.
Further Interview Details and Summit
The source points readers to the full interview and a YouTube version of the conversation for Allen’s extended discussion of correctness, language design, workloads and security. No product launch, policy change or follow-up research is announced in the supplied material.
The separate event announcement says applications are open for The Pragmatic Summit in San Francisco on Feb. 10. The report does not specify a year in the supplied excerpt, so the event date should be read as stated there rather than assumed to refer to a particular future calendar year.
Key Questions
Who is Sean Allen?
Allen is identified in The Pragmatic Engineer as a distinguished engineer at Antithesis and a core contributor to Pony, a programming language designed for concurrency. The article also cites his experience with distributed systems, stream processing and confidential computing.
How does Allen define software correctness?
He describes it as whether a program does what is expected of it. He discusses invariants as guarantees about behavior, while noting that teams may not know their expectations clearly until software fails.
What does Allen say about software testing?
Allen argues that manual testing is a poor substitute for designs that prevent invalid states from being expressed. He also recommends repeatable workloads that exercise a system multiple times, rather than depending only on unit tests.
Does the interview offer a fix for supply-chain attacks?
No. Allen says there is no single or simple fix. The source describes a tension between stronger language-level defenses and the limited popularity of languages that offer them, but does not provide a complete defense plan.
Was the interview sponsored by Antithesis?
The article says Antithesis sponsors the podcast, but states that the interview itself was not sponsored by Antithesis.
Source: newsletter.pragmaticengineer.com
