Post details
Happy ‘flying ant day’ to all those who celebrate, personally I stopped after I learnt it was just invented by Hallmark as a ploy to sell more cards.
This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:
Happy ‘flying ant day’ to all those who celebrate, personally I stopped after I learnt it was just invented by Hallmark as a ploy to sell more cards.
Between and I took 10365 steps.
Avoiding naming Go packages after common nouns like <code>rate</code> or <code>server</code> so that they don’t clash with variable names, and how to find a more fitting name for them instead.
Today, came across a Go package literally named "event". Such bland naming doesn't just hurt users, it hurts the package because being hard to google makes it less likely to be adopted. Ultra-generic naming isn't cool. It's just bad. For the love of god: https://brandur.org/fragments/go-no-common-nouns
Chris Anderson joins the show. You may recognize Chris from the early days of CouchDB and Couchbase. Back when the world was just waking up to NoSQL, Chris was at the center of it all, shaping how developers think about data distribution and offline-first architecture. These days, Chris is working on Vibes.diy and Fir...
ngrok Go SDK v2 released🚁 Go 1.25 interactive tour by Anton ZhiyanovJSON evolution in Go: from v1 to v2 by Anton Zhiyanov📘 Free eBook: Data Serialization in Go by Jonathan HallJSON BenchmarksLightning Round🐍 charm FangYouTube short: CoPilot API is written in Go⌨️ Typst: Compose text fasterJeremy...
Between and I took 5869 steps.
This week on The Business of Open Source, I spoke with Nick Veenhof, Director of Contributor Success at GitLab. GitLab has probably the most well-articulated open source strategy out there, and we talked about the two main prongs of that strategy, the co-create strategy and the dual flywheel...
Between and I took 3359 steps.
Listen to Still Panicking: How to Pass your Theory Test from Nobody Panic. Still Panicking: Stevie has been smashing it in the latest series of Taskmaster. To celebrate, this week we look back at some practical How-Tos to help guide you through tasks of your own.Stevie recently passed and has many thoughts. Tessa passed a couple of decades ago before there was an app. If you’ve been putting off booking your theory test because you’re worried about failing, or have it looming in a few weeks, this is the episode for you.Recorded and edited by Aniya Das for Plosive.Photos by Marco Vittur, jingle by David Dobson.
Tony Holdstock-Brown is the CEO and founder of Inngest, a tool to run AI and backend workflows at scale.This episode is brought to you by WorkOS. If you're thin...
Between and I took 4450 steps.
Ah nice! I remember having that magically work in bash
before but not have it set on zsh
- that's another good option
This week on The Business of Open Source I talked with Alya Abbott, COO of Zulip, about managing community contributors. This is a hot topic for open source companies — and for that matter, open source projects in general, including those that aren’t being monetized in any way. It’s a bit of a...
Me, all day yesterday to my kids: it's hot commie summer lmao and everyone wants merch 15, this morning: oh btw I made this last night [contains quote post or other embedded content]
Between and I took 4852 steps.
Go 1.25rc1 releasedOpinion: Go should be more opinionated by Elton MinettoBlog: HTTP QUERY and Go by Kevin McDonaldInterview with Redowan DelowarBlog post: You probably don't need a DI frameworkBlogFx dependency injection framework for GoBlog: How I program with agents
Kebab has already been skewered? 😝
Between and I took 5010 steps.
Jerod tells Adam about how bad he hates the taste of Gin, sips on some Generative A Rye (on the rocks), they open the comments section for a bit, and then land the plane talking about being alone, naked, and afraid.
Between and I took 4355 steps.
In this episode, Abi Noda speaks with Gilad Turbahn, Head of Developer Productivity, and Amy Yuan, Director of Engineering at Snowflake, about how their team builds and sustains operational excellence. They break down the practices and principles that guide their work—from creating two-way...
Between and I took 10897 steps.
I'm joined by Philippe Ombredanne, creator of the Package URL (PURL), to discuss the surprisingly complex and messy problem of simply identifying open source software packages. We dive into how PURLs provide a universal, common-sense standard that is becoming essential for the future of SBOMs and securing the software supply chain. The show notes and blog post for this episode can be found at
If you, a business, are reliant on an open source project to function it is YOUR responsibility to assess and ensure the health of that project by either contributing to it yourself or by using an alternative if project health cannot be guaranteed.
Today's history lesson is about the non-markup language platform engineers love to hate, YAML Ain't Markup Language (YAML). Ingy tells us all about how and why it started, how it evolved over time, and what's happening next with YS. Note: sorry about the audio issues in this episode. We did our...
Between and I took 7221 steps.
I love this and I’m stoked about this, but I feel for OSS communities that don’t have the outsized impact and leverage of CNCF. This wouldn’t have happened to anyone else, I suspect [contains quote post or other embedded content]
Between and I took 3309 steps.
I have never passed a single LeetCode-type interview. Because I didn't ever have to use this skill professionally & consider it ridiculous in the first place. That said, I have this interview today & I didn't have enough time to prepare. Yolo 🤪 Failing is still practice!
Jerod is joined by Carson Gross, the creator of htmx –a small, zero-dependency JavaScript library that he says, "completes HTML as a hypertext". Carson built it because he's big on hypermedia, he even wrote a book called Hypermedia Systems. Carson has a lot of strong opinions weakly held that we dive into in this conve...
Between and I took 7366 steps.
A few years ago, I quietly adopted a small principle that has changed how I think about publishing on my website. It's a principle I've been practicing for a while now, though I don't think I've ever …
Between and I took 2407 steps.
The CLI starter kit. Contribute to charmbracelet/fang development by creating an account on GitHub.
In this episode of The Tech Trek, Amir sits down with Matt Moore, CTO and co-founder of Chainguard, to explore the escalating importance of software supply chain security. From Chainguard’s origin story at Google to the systemic risks enterprises face when consuming open source, Matt shares the lessons, best practices, and technical innovations that help make open source software safer and more reliable. The conversation also touches on AI’s impact on the attack surface, mitigating threats with engineering rigor, and why avoiding long-lived credentials could be your best defense.🔑 Key Takeaways:Security Starts with Engineering: Doing engineering right makes security (and even compliance) much easier.Control the Full Chain: Building from source and applying best practices at every build stage significantly reduces exposure to CVEs.Attackers Exploit the Edges: Most attacks start small—with a leaked credential or compromised dependency—and cascade through the ecosystem.AI Introduces New Vectors: As AI tools integrate deeper into dev workflows, they bring both value and new risks that require thoughtful containment.You Can’t Leak What You Don’t Have: Eliminating long-lived credentials is one of the simplest and most effective ways to reduce breach risk.⏱ Timestamped Highlights:00:45 – What Chainguard does: securing open source consumption and curating safe containers.02:56 – Chainguard’s origin story and co-founders’ experience at Google.06:50 – Building minimal, hardened container images from source to mitigate CVEs.09:40 – Real-world example: how compiler hardening flags protected Chainguard from a high-severity CVE.10:59 – The invisible sprawl of open source in enterprise stacks—from Kubernetes to AWS SDKs.15:45 – How leaked credentials power cascading supply chain attacks.22:30 – “You can't leak what you don't have”: Chainguard's credential-less auth approach.24:30 – Most breaches come from known vulnerabilities—not zero-days.25:38 – AI and security: new use cases, new threats, and the need for explainability.30:41 – AI adoption in enterprises: security best practices still apply, just to new tools and risks.34:43 – Learn more at chainguard.dev and explore hardened images at images.chainguard.dev.💼 Career Tips (from the episode):Don’t wait for zero-days: Most real-world breaches stem from unpatched, well-known vulnerabilities. Ship secure, stay patched.Build from source: If you're in a security or DevOps role, aim to build and control your stack from the source code up—this provides auditability and trust.Engineering rigor is a differentiator: Whether you're launching a startup or working in enterprise tech, applying fundamental engineering principles helps you scale securely.📚 Resources Mentioned:🛡️ OpenSSF Projects – e.g., SIGstore, Scorecards, SLSA.🛠 Projects Mentioned: Kubernetes, Istio, Flux, Tekton, Cert-Manager, Cloud Code.💬 Quote of the Episode:“If you do engineering right, security becomes easier. And if you do security right, compliance becomes easier.” — Matt Moore
Utpal Nadiger is the cofounder of Digger.dev. Digger built a popular open source IaC orchestration tool. Their new product Infrabase is an AI DevOps agent that ...
Between and I took 7145 steps.
In this episode, Michael Lieberman, Co-founder and CTO of Kusari, walks us through the intersection of open source software and security. We discuss Mike's extensive involvement in OpenSSF projects like SLSA and GUAC, which provide essential frameworks for securing the software development life cycle (SDLC) and managing software supply chains. He explains how these tools help verify software provenance and manage vulnerabilities. Additionally, we explore regulatory concerns such as the Cyber Resilience Act (CRA) and the vital role of the recently released Open SSF Security Baseline (OSPS Baseline) in helping organizations comply with such regulations. Mike also shares insights into the evolution of open source security practices, the importance of reducing complexity for developers, and the potential benefits of orchestrating security similarly to Kubernetes. We conclude with a look at upcoming projects and current pilots aiming to simplify and enhance open source security. 00:00 Introduction and Guest Welcome 00:19 Mike's Background and Role in Open Source 01:35 Exploring SLSA and GUAC Projects 04:57 Cyber Resiliency Act Overview 06:54 OpenSSF Security Baseline 11:29 Encouraging Community Involvement 18:39 Final Thoughts Resources: OpenSSF's OSPS Baseline GUAC SLSA KubeCon Keynote: Cutting Through the Fog: Clarifying CRA Compliance in C... Eddie Knight & Michael Lieberman Guest: Michael Lieberman is co-founder and CTO of Kusari where he helps build transparency and security in the software supply chain. Michael is an active member of the open-source community, co-creating the GUAC and FRSCA projects and co-leading the CNCF’s Secure Software Factory Reference Architecture whitepaper. He is an elected member of the OpenSSF Governing Board and Technical Advisory Council along with CNCF TAG Security Lead and an SLSA steering committee member.
Deepak Prabhakara is the CEO and Co-founder of BoxyHQ. BoxyHQ enables you to add plug-and-play enterprise-ready features to your SaaS product.What we coverAn in...