Datasets:
File size: 3,863 Bytes
795d41b | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 | • Jeff Lindsay's background and experience • Discussion of his current projects and goals • Comparison of US vs. European perspective on old buildings • Mention of various open source projects, including Flynn, Dokku, Envy, Docker, OpenStack, webhooks, DevjaVu, and localtunnel • Building sustainable self-running services with open-source infrastructure • The importance of empowering users to build their own automation and custom solutions • Critique of using artificial intelligence (AI) for automation, preferring basic techniques instead • Composable software and visual tools like Microsoft Flow and WebPipes for easy automation • Designing systems that balance high-level interfaces with low-level customization options • Infrastructure development for building distributed systems and cloud platforms, including Docker and Kubernetes • Frustration with platform-as-a-service complexity • Operator pattern for abstracting away Kubernetes complexity • Criticism of corporate interests influencing open-source projects • Analysis paralysis due to numerous options and features • Desire for a simpler infrastructure approach, such as running containers in Docker • Moving on from complex technologies like Kubernetes once they become mainstream • Evolution of event handling and serverless computing • Comparison of AWS Lambda and other services • Introduction to durable functions for workflow automation • Discussion of Go programming language and its philosophy • Critique of complexity in software development and need for simpler systems • Importance of interfaces and two-way conversations in software design • Hook-based extensibility in software composition • Issue tracking system integrated with versioning • Hook-based interface for component-oriented software development • Dependent injection and configuration • Com library (GliderLabs Com) for building component-oriented software in Go • Wiki example demonstrating the power of com library • Standard Com library for common components like daemon management, HTTP, sessions, and authentication • Console component for wrapping up authentication • Command.io rebuild as a goal using com library • Function as a service concept with command-line interface • Power of SSH protocol for building complex systems and protocols • SSH library for Go (GliderLabs SSH) and its ease of use • Comparison to HTTP/2 and other protocols • Using interfaces in Go to build abstractions and simplify code • File system implementations, including Afero and 9P protocol • Mounting 9P file systems directly in Linux kernel without extra daemons or extensions • Custom file systems using network file system API (e.g. 9P) • Designing APIs with interfaces in Go • The benefits of using interfaces for abstraction and decoupling • The importance of well-designed interfaces for reusable software • Discussion of the Go Commons project and its emphasis on starting with interfaces • Using custom resource definitions (CRDs) with Kubernetes to simplify monitoring and metrics collection with Prometheus • Docker development environments • Google Working Group GreaterCommons courses for learning Go • Shoutouts to contributors, including spf13 (Steve Francia) and Todd McLeod • Open source project management and collaboration through pull requests and merge processes • Show highlights from past episodes and discussing guest appearances • The podcast has 273 episodes and a producer who pulls the plug at around 2-3 minutes. • Scott Mansfield is mentioned as having been on the show twice. • Guest hosts are sometimes used when regular hosts travel. • Jeff Lindsay's projects and work were discussed. • The episode was wrapping up due to time constraints. |