Gesamtlänge aller Episoden: 1 day 12 hours 22 minutes
Kevin and Andy answer Joe’s noob questions about development including the differences between compiled and interpreted languages, C vs C++, why the Linux kernel is written in C, Go vs Rust, and what memory safety means.
We are joined by Drew DeVault to discuss his programming language called Hare, which aims for 100 years of forwards compatibility. We mentioned Drew’s blog posts Can I be on your podcast? and It takes a village Kolide Kolide ensures that if a d...
How we first learned to code, and how we learn new technologies now. Snake in Terraform Snake in lots of languages Web server in Sinclair BASIC Kolide Kolide ensures that if a device isn’t secure it can’t access your apps.
What we’ve learned over the years about the interview process for software development jobs, both as the applicant and the interviewer. Kolide Kolide ensures that if a device isn’t secure it can’t access your apps. It’s Device Trust for Okta.
The automation tools we use in our development and why we use them. Plus how to engage with your project’s community – both in real time, and asynchronously. Kolide Kolide ensures that if a device isn’t secure it can’t access your apps.
Andy Balaam joins us to talk about accepting contributions from devs with varying levels of experience. When to invest the time to mentor them, why documentation is important, how automated tools fit in, being willing to decline some contributions,
How we use AI coding assistants like GitHub Copilot, what they have done to the development industry, what might happen in the future, and the ethics of the whole thing. With guest host Linus. Kolide Kolide ensures that if a device isn’t secure i...
We follow up on last episode with some clarifications from Amolith about code collaboration. Plus we get into development workflows in general, code review, the paradigms we couldn’t do without, and more. With guest host Linus.
When it comes to collaboration workflows, Amolith dislikes the pull request model that GitHub made popular and much prefers the email/patch-based approach. Kevin does his best to get to the bottom of why, and Joe wonders if it might come down to dislik...
Linux Downtime is now Linux Dev Time! In this first episode we talk about “sharpening our tools” – changing your dev tools, trying out new languages, using existing code vs writing something new, how to get over creative blocks, and more.