Jon Seager
Software engineer and engineering leader at Canonical, working on Ubuntu; writes about his homelab, Nix and tooling at jnsgr.uk.
Jon Seager did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
Filter All topics · Newest first
-
Their wordsSoftware teams that don't release software are broken software teams.
-
Their wordsBut perhaps most obviously, when you don't release often, your team gets worse at releasing.
-
Their wordsPerformance management is often associated with something going wrong, but it should be a continuous process, conducted in regular one-to-one meetings where short-, medium- and long-term goals are set and assessed, feedback is given (both ways!) and issues are addressed proactively.
- 5 weeks earlier
-
Our reading
Rewriting mature C code from scratch is expensive, risky, and rarely produces clear improvements.
Their wordsRewrites have long been expensive and risky, and do not often materialise obvious improvements.
↗Investing in automated C to Rust translationjnsgr.uk 1st of 3 in this piece
-
Their wordsplausible-looking output is not evidence that the translated program behaves like its source.
↗Investing in automated C to Rust translationjnsgr.uk 2nd of 3 in this piece
-
AI alignmentcode generationsoftware quality
Their wordsGenerated code should be treated as untrusted until there is evidence that it preserves the desired behaviour.
↗Investing in automated C to Rust translationjnsgr.uk 3rd of 3 in this piece
- 7 weeks earlier
-
Their wordsFirefox and Chromium have mature, browser-specific infrastructure for certificate revocation and related PKI data, but system utilities, package managers, language runtimes and many command-line tools have historically lacked a consistent mechanism for checking whether a publicly trusted TLS certificate has been revoked.
- 4 weeks earlier
-
Their wordsAgents need contained workspaces, clear boundaries around host access, and environments that can be torn down, recreated and shared without much ceremony.
- 5 weeks earlier
-
Their wordsAI is not going to take software engineering jobs at Canonical, but other software engineers who are highly competent with AI tools certainly could.
-
Their wordsDelegating elements of Site Reliability Engineering to an agent does not necessarily introduce an entirely new class of risk; it should inherit the constraints of existing production systems.
-
Their wordsThere will always be bigger models and smaller models, and those with more compute will be able to get more done than those with less compute, but the gap will begin to close.
- 5 weeks earlier
-
Their wordsKeeping accurate time is a critical system function, not least because it involves constant interaction with the internet and forms the basis for cryptographic verification in protocols such as Transport Layer Security (TLS).
- 2 weeks earlier
-
Their wordsPasskeys are phishing-resistant and significantly more difficult to brute-force both from an academic and a practical standpoint
-
LLMscoding agentssoftware quality
Their wordsIf you care about such constraints (function length, etc.), encode them as lints rather than hoping the agent internalises your preferences.
-
coding agentsdeveloper toolssoftware quality
Their wordsI think the key to useful output from these tools is that you remain the driver.
- 3 weeks earlier
-
Their wordsA correctly configured TLS server should not only send its own certificate, but also the intermediate certificates needed to chain back to a trusted root.