Tim Hinrichs

/*! elementor - v3.14.0 - 26-06-2023 */.elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}				Enabling authorization policies across disparate cloud-native environments such as containers, microservices and modern application delivery infrastructure is complex and can be a roadblock for software engineering teams.Open Policy Agent, or OPA, is an open, declarative, policy-as-code approach to authorization that reduces security and compliance burden for engineering teams.  Business context is translated into declarative policy statements. These policy statements are compiled into code and deployed as agents that can be injected into any process, such as an API gateway, Kubernetes provisioning service, public cloud access controls, or continuous delivery automation service.Styra created and contributed OPA to the Cloud Native Computing Foundation where it is a graduated project with over 130M downloads to date and is used by large companies. Styra’s enterprise commercial offering, Declarative Authorization Service (DAS), is specifically designed for OPA and includes the ability to author policies, preview impacts of new policies, and document the history of old policies, all through a single view.Tim Hinrichs, CTO and founder of Styra, joins the show today to discuss how to make authorization policies easier to author, distribute, and monitor.One note of disclosure to be aware of: Styra is a portfolio company of Capital One Ventures, the strategic investing arm of Capital One. Views and questions expressed in this podcast and related material are my own, or those of my guest, and do not reflect the views of Capital One Ventures or its respective affiliates.FOLLOW Jocelyn: twitter.com/jocelynbyrne Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Cloud-native Authorization with Tim Hinrichs appeared first on Software Engineering Daily.

/*! elementor - v3.14.0 - 26-06-2023 */ .elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}				<a href="https://i0.wp.com/softwareengineeringdaily.com/wp-content/uploads/2022/08/Tim-Hinrichs-2.png" rel="nofollow" target="_blank"></a>Enabling authorization policies across disparate cloud-native environments such as containers, microservices and modern application delivery infrastructure is complex and can be a roadblock for software engineering teams.Open Policy Agent, or OPA, is an open, declarative, policy-as-code approach to authorization that reduces security and compliance burden for engineering teams.  Business context is translated into declarative policy statements. These policy statements are compiled into code and deployed as agents that can be injected into any process, such as an API gateway, Kubernetes provisioning service, public cloud access controls, or continuous delivery automation service.<a href="https://www.styra.com/" rel="nofollow" target="_blank">Styra</a> created and contributed OPA to the Cloud Native Computing Foundation where it is a graduated project with over 130M downloads to date and is used by large companies. Styra’s enterprise commercial offering, Declarative Authorization Service (DAS), is specifically designed for OPA and includes the ability to author policies, preview impacts of new policies, and document the history of old policies, all through a single view.<a href="https://twitter.com/tlhinrichs" rel="nofollow" target="_blank">Tim Hinrichs</a>, CTO and founder of Styra, joins the show today to discuss how to make authorization policies easier to author, distribute, and monitor.One note of disclosure to be aware of: Styra is a portfolio company of <a href="https://growthventures.capitalone.com/" rel="nofollow" target="_blank">Capital One Ventures</a>, the strategic investing arm of Capital One. Views and questions expressed in this podcast and related material are my own, or those of my guest, and do not reflect the views of Capital One Ventures or its respective affiliates.FOLLOW Jocelyn: <a href="https://twitter.com/jocelynbyrne" rel="nofollow" target="_blank">twitter.com/jocelynbyrne</a> Sponsorship inquiries: <a href="sponsor@softwareengineeringdaily.com" rel="nofollow" target="_blank">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2022/08/09/cloud-native-authorization-with-tim-hinrichs/" rel="nofollow" target="_blank">Cloud-native Authorization with Tim Hinrichs</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Cloud-native Authorization with Tim Hinrichs

This episode is hosted by Alex DeBrie. Alex is the author of The DynamoDB Book, the comprehensive guide to data modeling with DynamoDB, as well as The DynamoDB Guide, a free guided introduction to DynamoDB. He runs a consulting company where he assists clients with DynamoDB data modeling, serverless architectures, and general AWS usage. You can find more of his work at alexdebrie.com. Nearly all new tech companies build in a public cloud and established companies are rapidly migrating to the cloud from their on-prem data centers. But this move to the cloud can lead to a visibility problem. Cloud Providers offer  not only Compute instances but also manage services like databases, blob storage, queues and more. It can be difficult for SRE teams and security departments to understand what is happening across a company’s cloud accounts. Yevgeny Pats is the creator of CloudQuery, an open source cloud asset inventory powered by SQL. CloudQuery allows you to ingest and structure the resources in your cloud accounts so that you can query them using SQL. This allows SRE teams to understand the source of specific resources while security teams can ensure compliance with policies.  In this episode we’ll discuss CloudQuery, Yevgeny’s entrepreneurial background and raising funding with an open source project Sponsorship inquiries: sponsor@softwareengineeringdaily.com.  The post Open-Source Cloud Asset Management with Yevgeny Pats appeared first on Software Engineering Daily.

<a href="https://i0.wp.com/softwareengineeringdaily.com/wp-content/uploads/2022/06/Yevgeny-Pats.png" rel="nofollow" target="_blank"></a>This episode is hosted by Alex DeBrie. Alex is the author of <a href="https://www.dynamodbbook.com/" rel="noopener nofollow" target="_blank">The DynamoDB Book</a>, the comprehensive guide to data modeling with DynamoDB, as well as <a href="https://www.dynamodbguide.com/" rel="noopener nofollow" target="_blank">The DynamoDB Guide</a>, a free guided introduction to DynamoDB. He runs a consulting company where he assists clients with DynamoDB data modeling, serverless architectures, and general AWS usage. You can find more of his work at <a href="http://alexdebrie.com/" rel="noopener nofollow" target="_blank">alexdebrie.com</a>. Nearly all new tech companies build in a public cloud and established companies are rapidly migrating to the cloud from their on-prem data centers. But this move to the cloud can lead to a visibility problem. Cloud Providers offer  not only Compute instances but also manage services like databases, blob storage, queues and more. It can be difficult for SRE teams and security departments to understand what is happening across a company’s cloud accounts. <a href="https://twitter.com/yevgenypats?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor" rel="nofollow" target="_blank">Yevgeny Pats</a> is the creator of<a href="https://twitter.com/cloudqueryio" rel="nofollow" target="_blank"> CloudQuery</a>, an open source cloud asset inventory powered by SQL. CloudQuery allows you to ingest and structure the resources in your cloud accounts so that you can query them using SQL. This allows SRE teams to understand the source of specific resources while security teams can ensure compliance with policies.  In this episode we’ll discuss CloudQuery, Yevgeny’s entrepreneurial background and raising funding with an open source project Sponsorship inquiries: <a href="sponsor@softwareengineeringdaily.com" rel="nofollow" target="_blank">sponsor@softwareengineeringdaily.com</a>. The post <a href="https://softwareengineeringdaily.com/2022/06/10/open-source-cloud-asset-management-with-yevgeny-pats/" rel="nofollow" target="_blank">Open-Source Cloud Asset Management with Yevgeny Pats</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Open-Source Cloud Asset Management with Yevgeny Pats

Zoe Steinkamp

InfluxDB is an open-source time-series database.  It’s maintained by InfuxData who offers a suite of products that help organizations gain insights from time-series data.  In this episode, I interview Zoe Steinkamp, Software Engineering and Developer Advocate at InfluxData.  We explore some of the common use cases for time-series databases such as IoT and some recent announcements such as the ability to run flux queries right inside VS Code. Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post InfluxData with Zoe Steinkamp appeared first on Software Engineering Daily.

InfluxDB is an open-source time-series database.  It’s maintained by InfuxData who offers a suite of products that help organizations gain insights from time-series data.  In this episode, I interview Zoe Steinkamp, Software Engineering and Developer Advocate at InfluxData.  We explore some of the common use cases for time-series databases such as IoT and some recent announcements such as the ability to run flux queries right inside VS Code. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/12/15/influxdata-with-zoe-steinkamp/" rel="nofollow" target="_blank">InfluxData with Zoe Steinkamp</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

InfluxData with Zoe Steinkamp

Alex Lichter

Alexander Lichter

When creating a website, there’s no shortage of choices for how to do it.  Builders must make strategic decisions about the language or framework they want to adopt.  An important first consideration for many is selecting a web application framework like React or Vue.  Motivated by a low page response time and good user experience, many developers want their site to be server-side rendered.  Nuxt.js is a free and open-source web application framework based on Vue.js which, among other benefits, brings server-side rendering to Vue.js developers. In this episode, I interview Alexander Lichter, founder of Development and Nuxt.js maintainer.  We discuss the features and Nuxt and what role it can play in your next web application. Show Notes:  https://blog.lichter.io/ https://vitejs.dev/ https://twitter.com/thealexlichter  Sponsorship inquiries: sponsor@softwareengineeringdaily.com     The post Nuxt.js with Alexander Lichter appeared first on Software Engineering Daily.

When creating a website, there’s no shortage of choices for how to do it.  Builders must make strategic decisions about the language or framework they want to adopt.  An important first consideration for many is selecting a web application framework like React or Vue.  Motivated by a low page response time and good user experience, many developers want their site to be server-side rendered.  Nuxt.js is a free and open-source web application framework based on Vue.js which, among other benefits, brings server-side rendering to Vue.js developers. In this episode, I interview Alexander Lichter, founder of Development and Nuxt.js maintainer.  We discuss the features and Nuxt and what role it can play in your next web application. Show Notes: <ul> <li><a href="https://blog.lichter.io/" rel="nofollow" target="_blank">https://blog.lichter.io/</a></li> <li><a href="https://vitejs.dev/" rel="nofollow" target="_blank">https://vitejs.dev/</a></li> <li><a href="https://twitter.com/thealexlichter" rel="nofollow" target="_blank">https://twitter.com/thealexlichter</a></li> </ul> Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/11/24/nuxt-js-with-alex-lichter/" rel="nofollow" target="_blank">Nuxt.js with Alexander Lichter</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Nuxt.js with Alexander Lichter

Minko Gechev

Angular is a free and open-source web application framework.  It’s maintained by the Angular team at Google.  It’s used by millions of web applications and has a strong ecosystem of core contributors and library builders. In this episode, I interview Minko Gechev, Developer Relations Lead at Google.  We explore several aspects of open-source software development, Tensorflow.js, Angular, and a few other things worth sticking around for. Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Angular Dev Tools with Minko Gechev appeared first on Software Engineering Daily.

Angular is a free and open-source web application framework.  It’s maintained by the Angular team at Google.  It’s used by millions of web applications and has a strong ecosystem of core contributors and library builders. In this episode, I interview Minko Gechev, Developer Relations Lead at Google.  We explore several aspects of open-source software development, Tensorflow.js, Angular, and a few other things worth sticking around for. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/11/05/angular-dev-tools-with-minko-gechev/" rel="nofollow" target="_blank">Angular Dev Tools with Minko Gechev</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Angular Dev Tools with Minko Gechev

Jonathan Ellis

Spencer Kimball

By most accounts, the first databases came on line in the 1960s. This class of software has continued to evolve alongside the technology it runs on and the applications it supports. In the early days, databases were typically closed source commercial products. Today, databases run in the cloud on distributed systems. Increasingly, the leading tools are open source yet frequently supported by a related commercial entity offering managed services and white glove support. In this episode, we interview Jonathan Ellis, CTO of DataStax and Spencer Kimball, CEO of Cockroach Labs about the current state of distributed databases and the open source ecosystem. Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Distributed Open Source Databases with Jonathan Ellis and Spencer Kimball appeared first on Software Engineering Daily.

By most accounts, the first databases came on line in the 1960s. This class of software has continued to evolve alongside the technology it runs on and the applications it supports. In the early days, databases were typically closed source commercial products. Today, databases run in the cloud on distributed systems. Increasingly, the leading tools are open source yet frequently supported by a related commercial entity offering managed services and white glove support. In this episode, we interview Jonathan Ellis, CTO of DataStax and Spencer Kimball, CEO of Cockroach Labs about the current state of distributed databases and the open source ecosystem. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/09/08/distributed-open-source-databases-with-jonathan-ellis-and-spencer-kimball/" rel="nofollow" target="_blank">Distributed Open Source Databases with Jonathan Ellis and Spencer Kimball</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Distributed Open Source Databases with Jonathan Ellis and Spencer Kimball

Brian Leonard

ETL stands for “extract, transform, load” and refers to the process of integrating data from many different sources into one location, usually a data warehouse. This process has become especially important for companies as they use many different services to collect and manage data.  The company Grouparoo provides an open source framework that helps you move data between your data warehouse and all of your cloud-based tools. This process of moving data back from the data warehouse to the applications is called reverse ETL, and is important for things like marketing campaigns and customer service. It easily integrates with your developer’s tools and is free and easy to install. In this episode we talk with Brian Leonard, CEO at Grouparoo. This interview will also be published as a video episode on our YouTube channel.  Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Grouparoo Open Source Data Tools with Brian Leonard appeared first on Software Engineering Daily.

ETL stands for “extract, transform, load” and refers to the process of integrating data from many different sources into one location, usually a data warehouse. This process has become especially important for companies as they use many different services to collect and manage data.  The company Grouparoo provides an open source framework that helps you move data between your data warehouse and all of your cloud-based tools. This process of moving data back from the data warehouse to the applications is called reverse ETL, and is important for things like marketing campaigns and customer service. It easily integrates with your developer’s tools and is free and easy to install. In this episode we talk with Brian Leonard, CEO at Grouparoo. This interview will also be published as a video episode on our <a href="https://www.youtube.com/channel/UCBKM3HATRILZyG9jGNJKGXQ" rel="noopener noreferrer nofollow" target="_blank">YouTube channel. </a> Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/08/26/grouparoo-open-source-data-tools-with-brian-leonard/" rel="nofollow" target="_blank">Grouparoo Open Source Data Tools with Brian Leonard</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Grouparoo Open Source Data Tools with Brian Leonard

William Morgan

In the late 1970s a printer at MIT kept jamming, resulting in regular pileups of print jobs in the printer’s queue. To solve this problem, some computer scientists wrote a software program that alerted every user in the backed up queue “The printer is jammed, please fix it.” When a man named Richard Stallmen was refused a copy of the program code, he resolved to create a publicly available operating system and the open source movement was born (opensource.com). Over 50 years later, open source has become a coding philosophy practiced by millions of software engineers around the world. Why is open source so popular? What difference has it really made in software engineering, and what major projects are open source? In this episode we talk to William Morgan, CEO at Buoyant and creator of the open source service mesh Linkerd. Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Publishing Open Source Code with William Morgan appeared first on Software Engineering Daily.

In the late 1970s a printer at MIT kept jamming, resulting in regular pileups of print jobs in the printer’s queue. To solve this problem, some computer scientists wrote a software program that alerted every user in the backed up queue “The printer is jammed, please fix it.” When a man named Richard Stallmen was refused a copy of the program code, he resolved to create a publicly available operating system and the open source movement was born (<a href="https://opensource.com/article/18/2/pivotal-moments-history-open-source" rel="nofollow" target="_blank">opensource.com</a>). Over 50 years later, open source has become a coding philosophy practiced by millions of software engineers around the world. Why is open source so popular? What difference has it really made in software engineering, and what major projects are open source? In this episode we talk to William Morgan, CEO at Buoyant and creator of the open source service mesh Linkerd. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/08/25/publishing-open-source-code-with-william-morgan/" rel="nofollow" target="_blank">Publishing Open Source Code with William Morgan</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Publishing Open Source Code with William Morgan

Matija Sosic

The term “boilerplate code” refers to code sections that are repeated across many projects with little to no variation. Every developer is familiar with boilerplate code, whether it be pom.xml files in Java or setting up React.js applications, tweaking boilerplate code for every project is inevitable. Actually, the company Wasp believes writing boilerplate code doesn’t have to be a part of web app development. Wasp is an open-source, declarative DSL for developers who want modern frontend, backend, and deployment experiences without writing boilerplate code. With Wasp, you can describe high-level features with Wasp DSL and write the rest of your logic in React, Node.js, and Prisma. In this episode, we talk to Matija Sosic, CEO and Co-Founder at Wasp. Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Wasp-Lang: Boilerplate Code with Matija Sosic appeared first on Software Engineering Daily.

The term “boilerplate code” refers to code sections that are repeated across many projects with little to no variation. Every developer is familiar with boilerplate code, whether it be pom.xml files in Java or setting up React.js applications, tweaking boilerplate code for every project is inevitable. Actually, the company Wasp believes writing boilerplate code doesn’t have to be a part of web app development. Wasp is an open-source, declarative DSL for developers who want modern frontend, backend, and deployment experiences without writing boilerplate code. With Wasp, you can describe high-level features with Wasp DSL and write the rest of your logic in React, Node.js, and Prisma. In this episode, we talk to Matija Sosic, CEO and Co-Founder at Wasp. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/08/05/wasp-lang-boilerplate-code-with-matija-sosic/" rel="nofollow" target="_blank">Wasp-Lang: Boilerplate Code with Matija Sosic</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Wasp-Lang: Boilerplate Code with Matija Sosic

Many startups today begin their life as an open-source project. Open source projects allow early adopters of a technology to experiment, to contribute code and feedback, and to shape the evolution of the project in its early stages. When a “community maintainer” company emerges to provide service offerings based on that project, its early customer base often consists of contributors to the open source project who already have experience with the technology, but want a more fully featured offering.  Orbit is a “community experience platform” that provides insights on activity for open-source and proprietary products. Orbit is founded on the “Orbit Model,” which it describes as a “framework for building high-gravity communities”- that is, developer communities with passionate and engaged contributors. The Orbit Model is offered as an alternative to traditional sales and marketing funnels that gives a focus on cultivating early adopters for a project. Patrick Woods and Josh Dzielak are the co-founders of Orbit. They join the show today to talk about the importance of an active and passionate community for projects, how Orbit helps Maintainers grow and shape their users’ experiences, and how they see Orbit evolving in the future. Sponsorship inquiries: sponsor@softwareengineeringdaily.com The post Developer Community Management with Patrick Woods and Josh Dzielak appeared first on Software Engineering Daily.

Many startups today begin their life as an open-source project. Open source projects allow early adopters of a technology to experiment, to contribute code and feedback, and to shape the evolution of the project in its early stages. When a “community maintainer” company emerges to provide service offerings based on that project, its early customer base often consists of contributors to the open source project who already have experience with the technology, but want a more fully featured offering.  Orbit is a “community experience platform” that provides insights on activity for open-source and proprietary products. Orbit is founded on the “Orbit Model,” which it describes as a “framework for building high-gravity communities”- that is, developer communities with passionate and engaged contributors. The Orbit Model is offered as an alternative to traditional sales and marketing funnels that gives a focus on cultivating early adopters for a project. Patrick Woods and Josh Dzielak are the co-founders of Orbit. They join the show today to talk about the importance of an active and passionate community for projects, how Orbit helps Maintainers grow and shape their users’ experiences, and how they see Orbit evolving in the future. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com" rel="noopener noreferrer">sponsor@softwareengineeringdaily.com</a> The post <a href="https://softwareengineeringdaily.com/2021/03/25/developer-community-management-with-patrick-woods-and-josh-dzielak/" rel="nofollow" target="_blank">Developer Community Management with Patrick Woods and Josh Dzielak</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Developer Community Management with Patrick Woods and Josh Dzielak

Open source technology episodes of Software Engineering Daily

Open Source Archives - Software Engineering Daily

Lee Coward

C# .NET is the framework that is most often used to write software for the Microsoft Windows operating system. For many years, the C# .NET framework was closed source, but Microsoft’s recent push towards open source has led to the creation of .NET Core, a fork of C# .NET composed of a small subset of features from the original C# .NET stack. This episode takes us through a history of .NET, with two program managers who have worked on .NET for many years–Immo Landwerth and Lee Coward. We also explored the present and future of .NET–discussing .NET Core and .NET usage on operating systems other than Microsoft Windows, which is another recent development. The post DotNet Core with Lee Coward and Immo Landwerth appeared first on Software Engineering Daily.

C# .NET is the framework that is most often used to write software for the Microsoft Windows operating system. For many years, the C# .NET framework was closed source, but Microsoft’s recent push towards open source has led to the creation of .NET Core, a fork of C# .NET composed of a small subset of features from the original C# .NET stack. This episode takes us through a history of .NET, with two program managers who have worked on .NET for many years–Immo Landwerth and Lee Coward. We also explored the present and future of .NET–discussing .NET Core and .NET usage on operating systems other than Microsoft Windows, which is another recent development. The post <a href="https://softwareengineeringdaily.com/2016/11/29/dotnet-core-with-lee-coward-and-immo-landwerth/" rel="nofollow" target="_blank">DotNet Core with Lee Coward and Immo Landwerth</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

DotNet Core with Lee Coward and Immo Landwerth

Dan Williams

Containers are widely used in projects that have adopted Docker, Kubernetes, or Mesos. Containers allow for better resource isolation and scalability. With all of the adoption of containers, companies like Red Hat, Google, and CoreOS are working on improved standards within the community. Standards are important to this community because of its pace of growth and the number of concurrent projects. If you heard our recent episode about the Linux Kernel’s open source governance, you know that having some rules in place will help encourage the right kind of creativity to thrive. In the world of containers, networking is not well addressed as it is highly environment specific. The Container Networking Interface is an effort to add specifications around how networks of containers can form.  Dan Williams is an engineer at Red Hat. In today’s episode, he explores the ideas behind the container networking interface, which gives insights into how the broader community of cloud native technologies is evolving as a whole. The post Container Networking with Dan Williams appeared first on Software Engineering Daily.

Containers are widely used in projects that have adopted Docker, Kubernetes, or Mesos. Containers allow for better resource isolation and scalability. With all of the adoption of containers, companies like Red Hat, Google, and CoreOS are working on improved standards within the community. Standards are important to this community because of its pace of growth and the number of concurrent projects. If you heard our recent episode about <a href="https://softwareengineeringdaily.com/2017/06/28/linux-kernel-governance-with-greg-kroah-hartman/" rel="nofollow" target="_blank">the Linux Kernel’s open source governance</a>, you know that having some rules in place will help encourage the right kind of creativity to thrive. In the world of containers, networking is not well addressed as it is highly environment specific. The Container Networking Interface is an effort to add specifications around how networks of containers can form. Dan Williams is an engineer at Red Hat. In today’s episode, he explores the ideas behind the container networking interface, which gives insights into how the broader community of cloud native technologies is evolving as a whole. The post <a href="https://softwareengineeringdaily.com/2017/07/24/container-networking-with-dan-williams/" rel="nofollow" target="_blank">Container Networking with Dan Williams</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Container Networking with Dan Williams

Alex Miller

Clojure is a dynamically typed functional language that runs on the JVM. Today’s guest Alex Miller gives us an overview of Clojure’s core functionality. Alex is a developer of Cognitect, and a founder of the the Strange Loop conference.     We discuss the data structures, garbage collection, and concurrency support. How does Clojure compare to other JVM languages like Scala and Groovy? How does Clojure copy immutable data structures without copying all of the data? How does a Clojure program get evaluated and converted to Java bytecode? These questions, and many others are discussed in this episode. The post Clojure with Alex Miller appeared first on Software Engineering Daily.

Clojure is a dynamically typed functional language that runs on the JVM. Today’s guest Alex Miller gives us an overview of Clojure’s core functionality. Alex is a developer of Cognitect, and a founder of the the Strange Loop conference. We discuss the data structures, garbage collection, and concurrency support. How does Clojure compare to other JVM languages like Scala and Groovy? How does Clojure copy immutable data structures without copying all of the data? How does a Clojure program get evaluated and converted to Java bytecode? These questions, and many others are discussed in this episode. The post <a href="https://softwareengineeringdaily.com/2016/08/04/clojure-with-alex-miller/" rel="nofollow" target="_blank">Clojure with Alex Miller</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Clojure with Alex Miller

Konrad Malawski

Akka is a toolkit for building concurrent, distributed, message-driven applications on the JVM. Akka provides an implementation of the actor model of concurrency, which simplifies concurrency by adding a lighter weight abstraction than threads and thread pools.  Konrad Malawski joins the show today to discuss Akka and reactive streams. Reactive streams is an initiative to provide a standard for asynchronous stream processing. This show goes deep into modern concurrent programming and is a great companion to some of the shows we have done about reactive programming.  The post Akka Reactive Streams with Konrad Malawski appeared first on Software Engineering Daily.

Akka is a toolkit for building concurrent, distributed, message-driven applications on the JVM. Akka provides an implementation of the actor model of concurrency, which simplifies concurrency by adding a lighter weight abstraction than threads and thread pools. Konrad Malawski joins the show today to discuss Akka and reactive streams. Reactive streams is an initiative to provide a standard for asynchronous stream processing. This show goes deep into modern concurrent programming and is a great companion to some of the shows we have done about reactive programming. The post <a href="https://softwareengineeringdaily.com/2016/08/22/akka-reactive-streams-with-konrad-malawski/" rel="nofollow" target="_blank">Akka Reactive Streams with Konrad Malawski</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Akka Reactive Streams with Konrad Malawski

Michael Hartl

“It really seemed like Rails just put everything together, so I thought well let’s give this thing a try, and I liked it.” Michael Hartl is the author of The Ruby on Rails Tutorial, a widely acclaimed guide to learning how to build Ruby on Rails webapps. Questions  You have a background in physics, including getting a PhD studying black hole dynamics – why did you switch careers to software? What was unique about the Ruby on Rails Tutorial when it first came out? Why didn’t Python and Django take off in the same way Ruby on Rails did? What do you think about the shift from Rails to full-stack JavaScript? Is there anything about Rails that you’re not a fan of? What are you building at your new company?  Links  OpenAI Ruby on Rails Tutorial Softcover Michael’s page   The post Learning Rails with Michael Hartl appeared first on Software Engineering Daily.

<h3>“It really seemed like Rails just put everything together, so I thought well let’s give this thing a try, and I liked it.”</h3> Michael Hartl is the author of The Ruby on Rails Tutorial, a widely acclaimed guide to learning how to build Ruby on Rails webapps. <h3>Questions</h3> <ul> <li>You have a background in physics, including getting a PhD studying black hole dynamics – why did you switch careers to software?</li> <li>What was unique about the Ruby on Rails Tutorial when it first came out?</li> <li>Why didn’t Python and Django take off in the same way Ruby on Rails did?</li> <li>What do you think about the shift from Rails to full-stack JavaScript?</li> <li>Is there anything about Rails that you’re not a fan of?</li> <li>What are you building at your new company?</li> </ul> <h3>Links</h3> <ul> <li><a href="https://openai.com/blog/introducing-openai/" rel="nofollow" target="_blank">OpenAI</a></li> <li><a href="https://www.railstutorial.org/" rel="nofollow" target="_blank">Ruby on Rails Tutorial</a></li> <li><a href="https://www.softcover.io/" rel="nofollow" target="_blank">Softcover</a></li> <li><a href="http://www.michaelhartl.com/" rel="nofollow" target="_blank">Michael’s page </a></li> </ul> The post <a href="https://softwareengineeringdaily.com/2016/01/11/learning-rails-with-michael-hartl/" rel="nofollow" target="_blank">Learning Rails with Michael Hartl</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Learning Rails with Michael Hartl

Sid Sijbrandij

GitLab is an open source platform for software development.  GitLab started with the ability to manage git repositories and now has functionality for collaboration, issue tracking, continuous integration, logging, and tracing. GitLab’s core business is selling to enterprises who want a self-hosted git installation, such as banks or other companies who prefer not to use a git service in the cloud. The vision for GitLab is to provide a platform for managing the full software development lifecycle, from code hosting to deployment–as well as tools for observability and project management.  Sid Sijbrandij is the CEO of GitLab and he joins the show to talk about the product, the business, and the company’s vision for the future. GitLab’s strategy is to offer a set of tools that work for developers out of the box, cutting down on time spent integrating each individual vendor. The post GitLab with Sid Sijbrandij appeared first on Software Engineering Daily.

GitLab is an open source platform for software development. GitLab started with the ability to manage git repositories and now has functionality for collaboration, issue tracking, continuous integration, logging, and tracing. GitLab’s core business is selling to enterprises who want a self-hosted git installation, such as banks or other companies who prefer not to use a git service in the cloud. The vision for GitLab is to provide a platform for managing the full software development lifecycle, from code hosting to deployment–as well as tools for observability and project management. Sid Sijbrandij is the CEO of GitLab and he joins the show to talk about the product, the business, and the company’s vision for the future. GitLab’s strategy is to offer a set of tools that work for developers out of the box, cutting down on time spent integrating each individual vendor. The post <a href="https://softwareengineeringdaily.com/2019/03/15/gitlab-with-sid-sijbrandij/" rel="nofollow" target="_blank">GitLab with Sid Sijbrandij</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

GitLab with Sid Sijbrandij

Yuri Shkuro

During 2015, Uber was going through rapid scalability. The internal engineering systems were constantly tested by the growing user base. Over the next two years, the number of internal services at Uber would grow from 500 to 2000, and standardizing the monitoring of all these different services became a priority. After working with a variety of available tools, Uber’s engineering team decided that something new needed to be built internally. Jaeger is an open source distributed tracing tool that provides observability features throughout Uber’s microservices architecture. Yuri Shkuro is an engineer at Uber, where he works on Jaeger and other infrastructure projects. He joins the show to discuss the history of engineering at Uber, the architecture of Jaeger, and the requirements for building and scaling a distributed tracing tool. Sponsorship inquiries: sponsor@softwareengineeringdaily.com Show Notes Mastering Distributed Tracing ANNOUNCEMENTS  FindCollabs is a place to find collaborators and build projects. We recently launched GitHub integrations. It’s easier than ever to find collaborators for your open source projects. And if you are looking for some people to start a project with, FindCollabs we have topic rooms that allow you to find other people who are interested in a particular technology, so that you can find people who are curious about React, or cryptocurrencies, or Kubernetes, or whatever you want to build with. Podsheets is an open source podcast hosting platform that we recently launched. We are building Podsheets with the learnings from Software Engineering Daily, and our goal is to be the best place to host and monetize your podcast. If you have been thinking about starting a podcast, check out podsheets.com.  New SEDaily app for iOS and for Android. It includes all 1000 of our old episodes, as well as related links, greatest hits, and topics. You can comment on episodes and have discussions with other members of the community. I’ll be commenting on each episode, so if you hear an episode that you have some commentary on, jump onto the app, or on SoftwareDaily.com to share your thoughts. And you can become a paid subscriber for ad free episodes at softwareengineeringdaily.com/subscribe. Altalogy is the company who has been developing much of the software for the newest app, and if you are looking for a company to help you with your mobile and web development, I recommend checking them out.     The post Jaeger: Distributed Tracing at Uber with Yuri Shkuro appeared first on Software Engineering Daily.

During 2015, Uber was going through rapid scalability. The internal engineering systems were constantly tested by the growing user base. Over the next two years, the number of internal services at Uber would grow from 500 to 2000, and standardizing the monitoring of all these different services became a priority. After working with a variety of available tools, Uber’s engineering team decided that something new needed to be built internally. Jaeger is an open source distributed tracing tool that provides observability features throughout Uber’s microservices architecture. Yuri Shkuro is an engineer at Uber, where he works on Jaeger and other infrastructure projects. He joins the show to discuss the history of engineering at Uber, the architecture of Jaeger, and the requirements for building and scaling a distributed tracing tool. Sponsorship inquiries: <a href="mailto:sponsor@softwareengineeringdaily.com">sponsor@softwareengineeringdaily.com</a> <h2>Show Notes</h2> <a href="https://www.shkuro.com/books/2019-mastering-distributed-tracing/" rel="nofollow" target="_blank">Mastering Distributed Tracing</a> <h2>ANNOUNCEMENTS</h2> <ul> <li><a href="https://findcollabs.com/" rel="nofollow" target="_blank">FindCollabs</a> is a place to find collaborators and build projects. We recently launched GitHub integrations. It’s easier than ever to find collaborators for your open source projects. And if you are looking for some people to start a project with, FindCollabs we have topic rooms that allow you to find other people who are interested in a particular technology, so that you can find people who are curious about React, or cryptocurrencies, or Kubernetes, or whatever you want to build with.</li> <li><a href="http://podsheets.com" rel="nofollow" target="_blank">Podsheets</a> is an open source podcast hosting platform that we recently launched. We are building Podsheets with the learnings from Software Engineering Daily, and our goal is to be the best place to host and monetize your podcast. If you have been thinking about starting a podcast, check out <a href="http://podsheets.com" rel="nofollow" target="_blank">podsheets.com</a>. </li> <li><a href="https://itunes.apple.com/us/app/software-engineering-daily/id1253734426?mt=8" rel="nofollow" target="_blank">New SEDaily app for iOS</a> and for <a href="https://play.google.com/store/apps/details?id=com.koalatea.sedaily" rel="nofollow" target="_blank">Android</a>. It includes all 1000 of our old episodes, as well as related links, greatest hits, and topics. You can comment on episodes and have discussions with other members of the community. I’ll be commenting on each episode, so if you hear an episode that you have some commentary on, jump onto the app, or on <a href="https://www.softwaredaily.com/" rel="nofollow" target="_blank">SoftwareDaily.com</a> to share your thoughts. And you can become a paid subscriber for ad free episodes at <a href="https://softwareengineeringdaily.com/subscribe" rel="nofollow" target="_blank">softwareengineeringdaily.com/subscribe</a>. <a href="http://altalogy.com" rel="nofollow" target="_blank">Altalogy</a> is the company who has been developing much of the software for the newest app, and if you are looking for a company to help you with your mobile and web development, I recommend checking them out.   </li> </ul> The post <a href="https://softwareengineeringdaily.com/2019/08/06/jaeger-distributed-tracing-at-uber-with-yuri-shkuro/" rel="nofollow" target="_blank">Jaeger: Distributed Tracing at Uber with Yuri Shkuro</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Jaeger: Distributed Tracing at Uber with Yuri Shkuro

Sean Li

Docker

“Docker has made containers much more accessible to developers, and the timing is actually very good because of the whole DevOps infrastructure as code movement.” Kitematic is an open source project built to simplify and streamline using Docker on a Mac or Windows machine. It allows users to get up and running on Docker with a single click, and provides a user interface that makes running and managing Docker files easy. Kitematic was acquired by Docker in March 2015. Sean Li is the co-founder and Chief Product Officer of Kitematic. He is now working on product design and developer experience at Docker. Questions  What was new about Docker that got people, including yourself, so excited? Is Docker a technology that is useful for consumers? Why did you build Kitematic? What type of user did you have in mind when you first designed the Kitematic UI? How do you see the Docker ecosystem evolving? What are the major technical bottlenecks in the Docker ecosystem? How do you use React components in a desktop app?  Links  Kitematic VirtualBox Docker Machine Github Desktop App Lightspeed Ventures Summer Fellowsship Hackers and Painters – Paul Graham Electron – Atom Sean on Twitter   The post Simplifying Docker with Sean Li appeared first on Software Engineering Daily.

<h3>“Docker has made containers much more accessible to developers, and the timing is actually very good because of the whole DevOps infrastructure as code movement.”</h3> Kitematic is an open source project built to simplify and streamline using Docker on a Mac or Windows machine. It allows users to get up and running on Docker with a single click, and provides a user interface that makes running and managing Docker files easy. Kitematic was acquired by Docker in March 2015. Sean Li is the co-founder and Chief Product Officer of Kitematic. He is now working on product design and developer experience at Docker. <h3>Questions</h3> <ul> <li>What was new about Docker that got people, including yourself, so excited?</li> <li>Is Docker a technology that is useful for consumers?</li> <li>Why did you build Kitematic?</li> <li>What type of user did you have in mind when you first designed the Kitematic UI?</li> <li>How do you see the Docker ecosystem evolving?</li> <li>What are the major technical bottlenecks in the Docker ecosystem?</li> <li>How do you use React components in a desktop app?</li> </ul> <h3>Links</h3> <ul> <li><a href="https://kitematic.com/" rel="nofollow" target="_blank">Kitematic</a></li> <li><a href="https://en.wikipedia.org/wiki/VirtualBox" rel="nofollow" target="_blank">VirtualBox</a></li> <li><a href="https://www.docker.com/docker-machine" rel="nofollow" target="_blank">Docker Machine</a></li> <li><a href="https://desktop.github.com/" rel="nofollow" target="_blank">Github Desktop App</a></li> <li><a href="http://lsvp.com/summer-fellowships/" rel="nofollow" target="_blank">Lightspeed Ventures Summer Fellowsship</a></li> <li><a href="http://www.paulgraham.com/hp.html" rel="nofollow" target="_blank">Hackers and Painters – Paul Graham</a></li> <li><a href="http://electron.atom.io/" rel="nofollow" target="_blank">Electron – Atom</a></li> <li><a href="https://twitter.com/lisean106" rel="nofollow" target="_blank">Sean on Twitter </a></li> </ul> The post <a href="https://softwareengineeringdaily.com/2016/01/05/simplifying-docker-with-sean-li/" rel="nofollow" target="_blank">Simplifying Docker with Sean Li</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Simplifying Docker with Sean Li

Curtis Yarvin

Urbit is a completely new way of looking at computing. Every user gets a personal server, which runs your apps, wrangles your connected devices, and defines your secure identity. Your urbit presents your whole digital life as a single web service. Urbit feels foreign and confusing for those of us coming from the traditional web because the normal paradigm is to iterate and paper over the problems of the current platform with new things built on top. Curtis Yarvin, the creator of Urbit, argues that the current model is too fundamentally broken for that to work. As he says: “the Internet as a client-server network has won. The Internet as a peer-to-peer network has failed.” This sounds like yet another quirky, overambitious developer side project–but Urbit has serious legs. The github repo has had 51 committers over its four years of activity. Last year, a public crowdsale of Urbit address space raised more than $200,000. Peter Thiel was an early investor in the project, perhaps partly due to the combination of persistence, technical skill, and unusual opinions of Curtis Yarvin. In this episode, Curtis and Galen Wolfe-Pauly join me for a conversation about Urbit–its strange computing platform and the contrarian philosophies that drive its creators. Show Notes Urbit Explanation  The post Urbit with Curtis Yarvin and Galen Wolfe-Pauly appeared first on Software Engineering Daily.

Urbit is a completely new way of looking at computing. Every user gets a personal server, which runs your apps, wrangles your connected devices, and defines your secure identity. Your urbit presents your whole digital life as a single web service. Urbit feels foreign and confusing for those of us coming from the traditional web because the normal paradigm is to iterate and paper over the problems of the current platform with new things built on top. Curtis Yarvin, the creator of Urbit, argues that the current model is too fundamentally broken for that to work. As he says: “the Internet as a client-server network has won. The Internet as a peer-to-peer network has failed.” This sounds like yet another quirky, overambitious developer side project–but Urbit has serious legs. The github repo has had 51 committers over its four years of activity. Last year, a public crowdsale of Urbit address space raised more than $200,000. Peter Thiel was an early investor in the project, perhaps partly due to the combination of persistence, technical skill, and unusual opinions of Curtis Yarvin. In this episode, Curtis and Galen Wolfe-Pauly join me for a conversation about Urbit–its strange computing platform and the contrarian philosophies that drive its creators. <h3>Show Notes <a href="https://youtu.be/g1qroWiZF90" rel="nofollow" target="_blank">Urbit Explanation</a> </h3> The post <a href="https://softwareengineeringdaily.com/2017/01/20/urbit-with-curtis-yarvin-and-galen-wolfe-pauly/" rel="nofollow" target="_blank">Urbit with Curtis Yarvin and Galen Wolfe-Pauly</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Urbit with Curtis Yarvin and Galen Wolfe-Pauly

Eric Seidel

Flutter is a project from Google that is rebuilding user interface engineering from the ground up.  Today, most engineering teams have dedicated engineering resources for web, iOS, and Android. These different platforms have their own design constraints, their own toolset, and their own programming languages. But each platform is merely building a user interface. Why should development across these three user surfaces be so different? This was the question that Eric Seidel was asking himself three years ago, when he co-founded the Flutter project. The Flutter project had a few rough starts, as the team tried to figure out exactly what layer of abstraction they were trying to provide.  Around that time, ReactJS and React Native were growing in popularity. Seeing the React projects provided some data points, and some inspiration. But Flutter takes a lower level approach to cross platform app development, by presenting a rendering layer and a runtime API that are interfacing with the hardware in the same way that OpenGL does.  In today’s episode, Eric joins the show to explain how the Flutter project came to life, and his lessons from starting an ambitious project that took several years to pick up steam. I enjoyed this episode because Flutter could have massive improvements for how quickly we can build apps–and also because Eric is a serious engineer and there are so many insights in this episode about computer science, software engineering, and project management. Transcript Transcript provided by We Edit Podcasts. Software Engineering Daily listeners can go to weeditpodcasts.com/sed to get 20% off the first two months of audio editing and transcription services. Thanks to We Edit Podcasts for partnering with SE Daily. Please click here to view this show’s transcript. The post Flutter with Eric Seidel appeared first on Software Engineering Daily.

Flutter is a project from Google that is rebuilding user interface engineering from the ground up. Today, most engineering teams have dedicated engineering resources for web, iOS, and Android. These different platforms have their own design constraints, their own toolset, and their own programming languages. But each platform is merely building a user interface. Why should development across these three user surfaces be so different? This was the question that Eric Seidel was asking himself three years ago, when he co-founded the Flutter project. The Flutter project had a few rough starts, as the team tried to figure out exactly what layer of abstraction they were trying to provide. Around that time, ReactJS and React Native were growing in popularity. Seeing the React projects provided some data points, and some inspiration. But Flutter takes a lower level approach to cross platform app development, by presenting a rendering layer and a runtime API that are interfacing with the hardware in the same way that OpenGL does. In today’s episode, Eric joins the show to explain how the Flutter project came to life, and his lessons from starting an ambitious project that took several years to pick up steam. I enjoyed this episode because Flutter could have massive improvements for how quickly we can build apps–and also because Eric is a serious engineer and there are so many insights in this episode about computer science, software engineering, and project management. <h2>Transcript</h2> Transcript provided by We Edit Podcasts. Software Engineering Daily listeners can go to <a href="https://weeditpodcasts.com/sed" rel="nofollow" target="_blank">weeditpodcasts.com/sed</a> to get 20% off the first two months of audio editing and transcription services. Thanks to We Edit Podcasts for partnering with SE Daily. Please <a href="https://softwareengineeringdaily.com/wp-content/uploads/2018/06/SED625-Flutter.pdf" rel="nofollow" target="_blank">click here to view this show’s transcript.</a> The post <a href="https://softwareengineeringdaily.com/2018/07/09/flutter-with-eric-seidel/" rel="nofollow" target="_blank">Flutter with Eric Seidel</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Flutter with Eric Seidel

Craig Holliday

You have probably missed some of the best episodes of Software Engineering Daily. If you listen to just a few episodes a week, it can be difficult to identify the high quality shows. And if you are new to the podcast, you have no idea how to find episodes that might appeal to you.  Software Engineering Daily has a discovery problem.  We have 600 episodes, and much of the content is evergreen. The shows we did a year ago on Apache Spark, or Ethereum, or ReactJS are still relevant today, and they get plenty of listens.  Keith and Craig Holliday built a recommendation system for Software Engineering Daily. Then they built a Software Engineering Daily iOS app to improve the experience of SE Daily listeners. You can use the SE Daily app to find the most popular episodes of this podcast, and to find episode recommendations based on what you have listened to. In this episode, Keith and Craig join the show to explain why they built an app for Software Engineering Daily. You can find all the code for the SE Daily app at github.com/softwareengineeringdaily in case you want to fork it for your own podcast–or if you want to contribute to it. Question of the Week: What is your favorite continuous delivery or continuous integration tool? Email jeff@softwareengineeringdaily.com and a winner will be chosen at random to receive a Software Engineering Daily hoodie.  The post Software Engineering Daily App with Keith and Craig Holliday appeared first on Software Engineering Daily.

You have probably missed some of the best episodes of Software Engineering Daily. If you listen to just a few episodes a week, it can be difficult to identify the high quality shows. And if you are new to the podcast, you have no idea how to find episodes that might appeal to you. Software Engineering Daily has a discovery problem. We have 600 episodes, and much of the content is evergreen. The shows we did a year ago on Apache Spark, or Ethereum, or ReactJS are still relevant today, and they get plenty of listens. Keith and Craig Holliday built a recommendation system for Software Engineering Daily. Then they built a <a href="https://itunes.apple.com/us/app/software-engineering-daily-podcast-app/id1253734426?mt=8" rel="nofollow" target="_blank">Software Engineering Daily iOS app</a> to improve the experience of SE Daily listeners. You can use the SE Daily app to find the most popular episodes of this podcast, and to find episode recommendations based on what you have listened to. In this episode, Keith and Craig join the show to explain why they built an app for Software Engineering Daily. You can find all the code for the SE Daily app at <a href="https://github.com/SoftwareEngineeringDaily" rel="nofollow" target="_blank">github.com/softwareengineeringdaily</a> in case you want to fork it for your own podcast–or if you want to contribute to it. Question of the Week: What is your favorite continuous delivery or continuous integration tool? Email jeff@softwareengineeringdaily.com and a winner will be chosen at random to receive a Software Engineering Daily hoodie.  The post <a href="https://softwareengineeringdaily.com/2017/09/08/software-engineering-daily-app-with-keith-and-craig-holliday/" rel="nofollow" target="_blank">Software Engineering Daily App with Keith and Craig Holliday</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Software Engineering Daily App with Keith and Craig Holliday

Marco Palladino

When a user makes a request to product like The New York Times, that request hits an API gateway. An API gateway is the entry point for an external request. An API gateway serves several purposes: authentication, security, routing, load balancing, and logging. API gateways have grown in popularity as applications have become more distributed, and companies offer a wider variety of services. If an API is public, and anyone can access it, you might need to apply rate limiting so that users cannot spam the API. If the API is private, the user needs to be authenticated before the request is fulfilled. Kong is a company that builds infrastructure for API management. The Kong API gateway is a widely used open source project, and Kong is a company built around supporting and building on top of the API gateway. Marco Palladino is the co-founder and CTO of Kong. He joins the show to tell the story of starting Kong eight years ago, and how the API gateway product evolved out of an API marketplace. Marco also discusses the architecture of Kong and his vision for how the product will develop in the future–including the Kong service mesh. The post Kong API Platform with Marco Palladino appeared first on Software Engineering Daily.

When a user makes a request to product like The <a href="https://softwareengineeringdaily.com/2017/11/30/react-and-graphql-at-new-york-times/" rel="nofollow" target="_blank">New York Times</a>, that request hits an API gateway. An API gateway is the entry point for an external request. An API gateway serves several purposes: authentication, security, routing, load balancing, and logging. API gateways have grown in popularity as applications have become more distributed, and companies offer a wider variety of services. If an API is public, and anyone can access it, you might need to apply rate limiting so that users cannot spam the API. If the API is private, the user needs to be authenticated before the request is fulfilled. Kong is a company that builds infrastructure for API management. The Kong API gateway is a widely used open source project, and Kong is a company built around supporting and building on top of the API gateway. Marco Palladino is the co-founder and CTO of Kong. He joins the show to tell the story of starting Kong eight years ago, and how the API gateway product evolved out of an API marketplace. Marco also discusses the architecture of Kong and his vision for how the product will develop in the future–including the Kong service mesh. The post <a href="https://softwareengineeringdaily.com/2019/01/04/kong-api-platform-with-marco-palladino/" rel="nofollow" target="_blank">Kong API Platform with Marco Palladino</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Kong API Platform with Marco Palladino

Craig McLuckie

The container management system Kubernetes was open sourced by Google with the intention of creating a cloud service based on the project. Today, the Kubernetes ecosystem is looking similar to the Android ecosystem, with different vendors providing different ways to use Kubernetes, from RedHat’s OpenShift to Google Container Engine.   Craig Mcluckie was a member of the team who originally devised Kubernetes, and he joins the show to talk about the origins of Kubernetes and where the project is headed, exploring both the technical architecture and Google’s business strategy around Kubernetes. The post Kubernetes Origins with Craig Mcluckie appeared first on Software Engineering Daily.

The container management system Kubernetes was open sourced by Google with the intention of creating a cloud service based on the project. Today, the Kubernetes ecosystem is looking similar to the Android ecosystem, with different vendors providing different ways to use Kubernetes, from RedHat’s OpenShift to Google Container Engine. Craig Mcluckie was a member of the team who originally devised Kubernetes, and he joins the show to talk about the origins of Kubernetes and where the project is headed, exploring both the technical architecture and Google’s business strategy around Kubernetes. The post <a href="https://softwareengineeringdaily.com/2016/07/20/kubernetes-origins-with-craig-mcluckie/" rel="nofollow" target="_blank">Kubernetes Origins with Craig Mcluckie</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Kubernetes Origins with Craig Mcluckie

Morgan Wilde

Every program gets compiled down to 1s and 0s before it can be executed against hardware. Before being translated to machine code, programs that are written in a language like Rust, Swift, or Java spend time in an intermediate representation.  In Java, this intermediate representation is Java bytecode. Many different languages–such as Scala–translate to Java bytecode, because there has been lots of optimization written to speed up Java bytecode. Java bytecode runs on the JVM–the Java Virtual Machine. LLVM is a project that draws inspiration from the Java Virtual Machine. LLVM originally meant “low level virtual machine” but today it is just called LLVM and describes a set of compiler tools. In today’s interview with Morgan Wilde, we explore how compilers work, how different processor hardware architectures present a problem for compilers, and why LLVM’s intermediate representation creates a layer of interoperability for any language that compiles down to that intermediate representation. Whether you are new to compilers or have experience, this episode will appeal to you. Morgan is an excellent teacher and his enthusiasm for the subject comes through. He has a 30-minute YouTube video–A Brief Introduction to LLVM that I highly recommend. The post LLVM with Morgan Wilde appeared first on Software Engineering Daily.

Every program gets compiled down to 1s and 0s before it can be executed against hardware. Before being translated to machine code, programs that are written in a language like Rust, Swift, or Java spend time in an intermediate representation. In Java, this intermediate representation is Java bytecode. Many different languages–such as Scala–translate to Java bytecode, because there has been lots of optimization written to speed up Java bytecode. Java bytecode runs on the JVM–the Java Virtual Machine. LLVM is a project that draws inspiration from the Java Virtual Machine. LLVM originally meant “low level virtual machine” but today it is just called LLVM and describes a set of compiler tools. In today’s interview with Morgan Wilde, we explore how compilers work, how different processor hardware architectures present a problem for compilers, and why LLVM’s intermediate representation creates a layer of interoperability for any language that compiles down to that intermediate representation. Whether you are new to compilers or have experience, this episode will appeal to you. Morgan is an excellent teacher and his enthusiasm for the subject comes through. He has a 30-minute YouTube video–<a href="https://www.youtube.com/watch?v=a5-WaD8VV38&amp;t=992s" rel="nofollow" target="_blank">A Brief Introduction to LLVM</a> that I highly recommend. The post <a href="https://softwareengineeringdaily.com/2017/04/10/llvm-with-morgan-wilde/" rel="nofollow" target="_blank">LLVM with Morgan Wilde</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

LLVM with Morgan Wilde

Blogging is more than 20 years old. Over that period of time, numerous publishing platforms have been created. Squarespace, Blogger, Medium, and Twitter are popular closed source platforms. WordPress has been the most popular open source blogging platform–and much of the Internet (including Software Engineering Daily) runs on WordPress. WordPress is a powerful platform. News companies, ecommerce websites, and many other kinds of businesses use WordPress as their central publishing tool. But WordPress has been around for 15 years–and there are some potential conflicts of interest between WordPress the open source project and WordPress.com (a company started to host WordPress websites). John O’Nolan was working as a WordPress developer when he decided to start a new publishing platform called Ghost. Five years later, the Ghost project is a success–with a thriving open source community, a profitable SaaS business, and companies like Digital Ocean and Mozilla using Ghost to host their blogs. John and I discussed his background with WordPress, what he wanted to do differently with Ghost, and the software architecture of Ghost. We also touched on the Ghost SaaS business and the management of the open source project. The post Ghost: Open Source Publishing Platform with John O’Nolan appeared first on Software Engineering Daily.

Blogging is more than 20 years old. Over that period of time, numerous publishing platforms have been created. Squarespace, Blogger, Medium, and Twitter are popular closed source platforms. WordPress has been the most popular open source blogging platform–and much of the Internet (including Software Engineering Daily) runs on WordPress. WordPress is a powerful platform. News companies, ecommerce websites, and many other kinds of businesses use WordPress as their central publishing tool. But WordPress has been around for 15 years–and there are some potential conflicts of interest between WordPress the open source project and <a href="http://WordPress.com" rel="nofollow" target="_blank">WordPress.com</a> (a company started to host WordPress websites). John O’Nolan was working as a WordPress developer when he decided to start a new publishing platform called Ghost. Five years later, the Ghost project is a success–with a thriving open source community, a profitable SaaS business, and companies like Digital Ocean and Mozilla using Ghost to host their blogs. John and I discussed his background with WordPress, what he wanted to do differently with Ghost, and the software architecture of Ghost. We also touched on the Ghost SaaS business and the management of the open source project. The post <a href="https://softwareengineeringdaily.com/2018/07/26/ghost-open-source-publishing-platform-with-john-onolan/" rel="nofollow" target="_blank">Ghost: Open Source Publishing Platform with John O’Nolan</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Ghost: Open Source Publishing Platform with John O’Nolan

Jeff Bezanson

Jeff Bezanson’s university thesis described the motivation for a new programming language. He discussed the shortcomings of “array based programming environments” and his desire to create a more performant language with the best qualities of Lisp, Python, Ruby, Perl, Mathematica, R, and C. The Julia Language is a high performance language designed to suit technical users that crave the flexibility to pick their own notation. The language has support for a wide variety of operators, allowing scientists to create domain specific equations that can be elegantly expressed as code. Jeff Bezanson joins the show to discuss his motivations for Julia, and how the language has evolved since he started working on it. The post Julia Language with Jeff Bezanson appeared first on Software Engineering Daily.

Jeff Bezanson’s university thesis described the motivation for a new programming language. He discussed the shortcomings of “array based programming environments” and his desire to create a more performant language with the best qualities of Lisp, Python, Ruby, Perl, Mathematica, R, and C. The Julia Language is a high performance language designed to suit technical users that crave the flexibility to pick their own notation. The language has support for a wide variety of operators, allowing scientists to create domain specific equations that can be elegantly expressed as code. Jeff Bezanson joins the show to discuss his motivations for Julia, and how the language has evolved since he started working on it. The post <a href="https://softwareengineeringdaily.com/2016/11/08/julia-language-with-jeff-bezanson/" rel="nofollow" target="_blank">Julia Language with Jeff Bezanson</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Julia Language with Jeff Bezanson

Tom Occhino

Facebook’s open source projects include React, GraphQL, and Cassandra. These projects are key pieces of infrastructure used by thousands of developers–including engineers at Facebook itself.  These projects are able to gain traction because Facebook takes time to decouple the projects from their internal infrastructure and clean up the code before releasing them into the wild. Facebook has high standards for what they are willing to release. Tom Occhino manages the React team at Facebook and works closely with engineers to determine what projects make sense to open source. In this episode, Preethi Kasireddy interviews Tom about how Facebook thinks about open source–what went right with React, why it makes sense for Facebook to continue to release new open source projects, and how full-time employees at Facebook interact with that open source codebase. We would love to get your feedback on Software Engineering Daily. Please fill out the listener survey, available on softwareengineeringdaily.com/survey. Also–Software Engineering Daily is having our third Meetup, Wednesday May 3rd at Galvanize in San Francisco. The theme of this Meetup is Fraud and Risk in Software. We will have great food, engaging speakers, and a friendly, intellectual atmosphere. To find out more, go to softwareengineeringdaily.com/meetup. Show Notes Pete Hunt: React: Rethinking best practices — JSConf EU 2013 The post Facebook Open Source with Tom Occhino appeared first on Software Engineering Daily.

Facebook’s open source projects include React, GraphQL, and Cassandra. These projects are key pieces of infrastructure used by thousands of developers–including engineers at Facebook itself. These projects are able to gain traction because Facebook takes time to decouple the projects from their internal infrastructure and clean up the code before releasing them into the wild. Facebook has high standards for what they are willing to release. Tom Occhino manages the React team at Facebook and works closely with engineers to determine what projects make sense to open source. In this episode, Preethi Kasireddy interviews Tom about how Facebook thinks about open source–what went right with React, why it makes sense for Facebook to continue to release new open source projects, and how full-time employees at Facebook interact with that open source codebase. We would love to get your feedback on Software Engineering Daily. Please fill out the listener survey, available on <a href="http://softwareengineeringdaily.com/survey" rel="nofollow" target="_blank">softwareengineeringdaily.com/survey</a>. Also–Software Engineering Daily is having our third Meetup, Wednesday May 3rd at Galvanize in San Francisco. The theme of this Meetup is Fraud and Risk in Software. We will have great food, engaging speakers, and a friendly, intellectual atmosphere. To find out more, go to <a href="http://softwareengineeringdaily.com/meetup" rel="nofollow" target="_blank">softwareengineeringdaily.com/meetup</a>. <h2>Show Notes</h2> <a href="https://www.youtube.com/watch?v=x7cQ3mrcKaY" rel="nofollow" target="_blank">Pete Hunt: React: Rethinking best practices — JSConf EU 2013</a> The post <a href="https://softwareengineeringdaily.com/2017/04/14/facebook-open-source-with-tom-occhino/" rel="nofollow" target="_blank">Facebook Open Source with Tom Occhino</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Facebook Open Source with Tom Occhino

Dan Abramov

React is a set of open source tools for building user interfaces. React was open sourced by Facebook, and includes libraries for creating interfaces on the web (ReactJS) and on mobile devices (React Native). React was released during a time when there was not a dominant frontend JavaScript library. Backbone, Angular, and other JavaScript frameworks were all popular, but there was not any consolidation across the frontend web development community. Before React came out, frontend developers were fractured into different communities for the different JavaScript frameworks.  After Facebook open sourced React, web developers began to gravitate towards the framework for its one-way data flow and its unconventional style of putting JavaScript and HTML together in a format called JSX. As React has grown in popularity, the React ecosystem has developed network effects. In many cases, the easiest way to build a web application frontend is to compose together open source React components. After seeing the initial traction, Facebook invested heavily into React, creating entire teams within the company whose goal was to improve React. Dan Abramov works on the React team at Facebook and joins the show to talk about how the React project is managed and his vision for the project.   RECENT UPDATES: The FindCollabs Open has started. It is our second FindCollabs hackathon, and we are giving away $2500 in prizes. The prizes will be awarded in categories such as machine learning, business plan, music, visual art, and JavaScript. If one of those areas sounds interesting to you, check out findcollabs.com/open! The FindCollabs Podcast is out! We are booking sponsorships for Q3, find more details at https://softwareengineeringdaily.com/sponsor/ The post Facebook React with Dan Abramov appeared first on Software Engineering Daily.

React is a set of open source tools for building user interfaces. React was open sourced by Facebook, and includes libraries for creating interfaces on the web (ReactJS) and on mobile devices (React Native). React was released during a time when there was not a dominant frontend JavaScript library. Backbone, Angular, and other JavaScript frameworks were all popular, but there was not any consolidation across the frontend web development community. Before React came out, frontend developers were fractured into different communities for the different JavaScript frameworks. After Facebook open sourced React, web developers began to gravitate towards the framework for its one-way data flow and its unconventional style of putting JavaScript and HTML together in a format called JSX. As React has grown in popularity, the React ecosystem has developed network effects. In many cases, the easiest way to build a web application frontend is to compose together open source React components. After seeing the initial traction, Facebook invested heavily into React, creating entire teams within the company whose goal was to improve React. Dan Abramov works on the React team at Facebook and joins the show to talk about how the React project is managed and his vision for the project. RECENT UPDATES: <a href="http://findcollabs.com/open" rel="nofollow" target="_blank">The FindCollabs Open has started. It is our second FindCollabs hackathon, and we are giving away $2500 in prizes. The prizes will be awarded in categories such as machine learning, business plan, music, visual art, and JavaScript. If one of those areas sounds interesting to you, check out findcollabs.com/open!</a> <a href="https://podcasts.apple.com/us/podcast/findcollabs-podcast/id1460158612" rel="nofollow" target="_blank">The FindCollabs Podcast is out!</a> <a href="https://softwareengineeringdaily.com/sponsor/" rel="nofollow" target="_blank">We are booking sponsorships for Q3, find more details at https://softwareengineeringdaily.com/sponsor/</a> The post <a href="https://softwareengineeringdaily.com/2019/05/16/facebook-react-with-dan-abramov/" rel="nofollow" target="_blank">Facebook React with Dan Abramov</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Facebook React with Dan Abramov

Henry Zhu

Different browsers consume JavaScript in different ways.  When a new version of JavaScript comes out, developers are eager to use the new functionality of that language version. But if you are writing frontend JavaScript code, that code needs to be interpretable by every browser that might consume it–whether the consumer is on an iPhone running Safari or a Windows machine running Internet Explorer 11. Babel is a transpiler for JavaScript. Babel allows new versions of JavaScript to be consumed by older browsers by translating new language features of JavaScript into code that is readable by an older JavaScript interpreter. Babel does this by parsing JavaScript code, creating an abstract syntax tree, and manipulating the AST to make that code comply with the old browser. Henry Zhu is a core maintainer of Babel and a full-time open source developer. In today’s episode, Henry explains how Babel works and its various applications. He also talks about life as a full-time open source developer, where he earns a living through Patreon and OpenCollective. The post Babel with Henry Zhu appeared first on Software Engineering Daily.

Different browsers consume JavaScript in different ways. When a new version of JavaScript comes out, developers are eager to use the new functionality of that language version. But if you are writing frontend JavaScript code, that code needs to be interpretable by every browser that might consume it–whether the consumer is on an iPhone running Safari or a Windows machine running Internet Explorer 11. Babel is a transpiler for JavaScript. Babel allows new versions of JavaScript to be consumed by older browsers by translating new language features of JavaScript into code that is readable by an older JavaScript interpreter. Babel does this by parsing JavaScript code, creating an abstract syntax tree, and manipulating the AST to make that code comply with the old browser. Henry Zhu is a core maintainer of Babel and a full-time open source developer. In today’s episode, Henry explains how Babel works and its various applications. He also talks about life as a full-time open source developer, where he earns a living through Patreon and OpenCollective. The post <a href="https://softwareengineeringdaily.com/2018/06/21/babel-with-henry-zhu/" rel="nofollow" target="_blank">Babel with Henry Zhu</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Babel with Henry Zhu

Sebastien Goasgoen

Modern architectures often consist of containers that run services. Those containers scale up and down depending on the demand for the services. These large software systems often use a technique known as event sourcing, where every change to the system is kept in an event log. When an event on the log is processed, several different data stores might be updated in response. In these architectures, containers are interacting with each other. Multiple databases are responding to events in the event log. To connect these systems together, engineers can write small functions to pass data around–you might call these small connecting functions “glue.” Glue functions are a great use for a serverless tool such as AWS Lambda or Google Cloud Functions. As these glue functions grow in popularity, there is an increased need for an open source way to deploy serverless functions. Sebastien Goasgoen works on Kubeless, a serverless execution tool built on top of Kubernetes. In this episode, we explore his take on the “serverless on Kubernetes” problem. This is a great companion episode to yesterday’s interview with Soam Vasani. Software Engineering Daily is looking for sponsors for Q3. If your company has a product or service, or if you are hiring, Software Engineering Daily reaches 23,000 developers listening daily. Send me an email: jeff@softwareengineeringdaily.com The post Event Driven Serverless with Sebastien Goasgoen appeared first on Software Engineering Daily.

Modern architectures often consist of containers that run services. Those containers scale up and down depending on the demand for the services. These large software systems often use a technique known as event sourcing, where every change to the system is kept in an event log. When an event on the log is processed, several different data stores might be updated in response. In these architectures, containers are interacting with each other. Multiple databases are responding to events in the event log. To connect these systems together, engineers can write small functions to pass data around–you might call these small connecting functions “glue.” Glue functions are a great use for a serverless tool such as AWS Lambda or Google Cloud Functions. As these glue functions grow in popularity, there is an increased need for an open source way to deploy serverless functions. Sebastien Goasgoen works on Kubeless, a serverless execution tool built on top of Kubernetes. In this episode, we explore his take on the “serverless on Kubernetes” problem. This is a great companion episode to yesterday’s interview with Soam Vasani. Software Engineering Daily is looking for sponsors for Q3. If your company has a product or service, or if you are hiring, Software Engineering Daily reaches 23,000 developers listening daily. Send me an email: jeff@softwareengineeringdaily.com The post <a href="https://softwareengineeringdaily.com/2017/06/13/event-driven-serverless-with-sebastian-goasgoen/" rel="nofollow" target="_blank">Event Driven Serverless with Sebastien Goasgoen</a> appeared first on <a href="https://softwareengineeringdaily.com" rel="nofollow" target="_blank">Software Engineering Daily</a>.

Event Driven Serverless with Sebastien Goasgoen

The best podcasts about ourselves as well as the world through the lense of Science. Specific topics include things about our brain, emotions to biology, physics and more!

Best Episodes on Science, Humans & The World

The best podcast episodes on global issues affecting everyone. Covering topics such as the #metoo movement, climate change, the impact of technology and some of the biggest global issues facing us right now. For anyone interested in learning more about the world, and some of the issues we're facing, pick an episode below and start listening! Add episodes you're interested into your queue below!