エピソード

  • Cloud infra, with Kurt Mackey (Fly.io) - S04E11

    Cloud infra, with Kurt Mackey (Fly.io) - S04E11
    2023/07/06
    In this episode, we speak with Kurt Mackey, CEO of Fly.io. We discuss what it's like running physical servers in data centers around the world, why they didn't build on top of the cloud, and what the philosophy is behind the focus on pure compute, networking, and storage primitives. Kurt sheds light on the regions where Fly.io is most popular, why they’re adding GPUs, and the technology that makes it all work behind the scenes.Hosted by David Mytton (Console) and Jean Yang (Akita Software).Things mentioned:Ars TechnicaY CombinatorMongoHQServerCentral (now Deft)MiamiNAPAWSThe Everything StoreVercelSimon WillisonDjango datasetChatGPTNvidiaFirecracker VMNomadPhoenixLiteFSSQLiteHacker NewsElixirDeno FreshRemixM2 MacBook Air Nvidia A100 GPU ABOUT KURT MACKEYKurt Mackey is the CEO of Fly.io, a company that deploys app servers close to your users for running full-stack applications and databases all over the world without any DevOps. He began his career as a tech writer for Ars Technica and learned about databases while building a small retail PHP app. He went to Y Combinator in 2011 where he joined a company called MongoHQ (now Compose) that hosted Mongo databases which he sold to IBM, before turning his attention to building Fly.io. Highlights: [Kurt Mackey]: The original thesis for this company was there's not really any good CDNs for developers. If you could crack that, it'd be very cool. The first thing we needed was servers in a bunch of places and a way to route traffic to them. What we wanted was AnyCast, which is kind of a part of the core internet routing technology. What it does is it offloads getting a packet to probably the closest server, to the internet backbones almost. You couldn't actually do AnyCast on top of the public cloud at that point. I think you can on top of AWS now. So we were sort of forced to figure out how to get our IPs, we were sort of forced into physical servers for that reason. For a couple of years, it felt like we got deeply unlucky because we had to do physical servers. You’d talk to investors, and they'd be like, “Why aren’t you just running on the public cloud and then saving money later?” Then last year, that flipped. Now, we're very interesting because we don't run on the public clouds.— [0:11:14 - 0:12:03] [Kurt Mackey]: I think there's another thing that we've probably all reckoned with since 2011; a lot of the abstractions were wrong. As the front end got more powerful, I think we tried a lot of different things for— and what we ended up doing was inflicting this weird distributed systems problem on frontend developers. So I think that, in some ways, we just have the luxury of ignoring a lot of things that people have been trying to figure out for 10 years because we probably think that's wrong at this point. So we happen to be doing well at a time when server-side rendering is all the rage in a front-end community, which is perfect for us and nobody really cares about shipping static files around in the same way. I think it's just evolutionary. We kind of have a different idea of what's right now and can do simpler things and then we'll probably get big and complicated in 10 years and be in the same situation again.— [0:18:25 - 0:19:11]Let us know what you think on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmyttonOr by email: hello@console.devAbout ConsoleConsole is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. Sign up for free at: https://console.dev
    続きを読む 一部表示
    36 分
  • Serverless databases, with Monica Sarbu (Xata) - S04E10

    Serverless databases, with Monica Sarbu (Xata) - S04E10
    2023/06/29

    In this episode, we speak with Monica Sarbu, CEO of Xata. We start with the philosophy behind serverless databases, why developers shouldn't need to think about relational databases, search, and analytics, whether the performance hit of accessing a database over HTTP matters, and how database branching works. She also talks about Xata’s plans for a global database, the company’s focus on UI developers, and what other databases are doing wrong.

    Hosted by David Mytton (Console) and Jean Yang (Akita Software).

    Things mentioned:

    • Xata
    • tupu.io
    • Elastic
    • PlanetScale
    • Quicker serverless Postgres connections
    • Cloudflare Workers
    • Airtable
    • Xata ChatGPT integration
    • Apple Mac

     

    ABOUT MONICA SARBU:

    Monica Sarbu is the Founder and CEO of Xata, a serverless database built for modern development. Prior to that, she worked on an open-source monitoring solution called Packetbeat which was acquired by Elastic in 2015. She is also the co-founder of tupu.io, a non-profit initiative that offers free mentorship to women, people of color, and other underrepresented groups in the tech industry.
     

    Highlights:
     

    [Monica Sarbu]: The idea of a single API is that because, like I said, this scenario happens in every company out there; when they start a new web application, they need to build this data platform internally. My thinking was why [does] every company out there need to reinvent the wheel when we can provide all this functionality: database, search functionality, analytics, time series data as well, and under a single API? This was the main purpose of having a single API.

    — [0:05:14 - 0:05:49]
     

    [Monica Sarbu]: I've seen that there are so many companies out there that are building their data platform on top of Airtable and they are developers. The reason behind that was that it's easier to use, and they had– While I was speaking with so many companies, I've seen so many hacks because they had hundreds of Airtables. They were synchronizing between them because you cannot really store a lot of data in one Airtable. My idea is — especially with serverless applications — that when you're building a web application, you have most of your logic in a lambda function so you cannot really use any of these databases and services that are out there, right? So Airtable was an easy-to-use approach but Airtable was not really meant to be built as a database. I've seen that there is a huge opportunity to build something that is as easy to use as Airtable but as scalable as a traditional database and also powerful as a traditional database.

    — [0:25:12 - 0:26:16]

     

    Let us know what you think on Twitter:

    https://twitter.com/consoledotdev

    https://twitter.com/davidmytton

    Or by email: hello@console.dev

    About Console

    Console is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. 

    Sign up for free at: https://console.dev
    続きを読む 一部表示
    29 分
  • Creating Julia, with Jeff Bezanson (JuliaHub) - S04E09

    Creating Julia, with Jeff Bezanson (JuliaHub) - S04E09
    2023/06/22
    In this episode, we speak with Jeff Bezanson, one of the co-creators of the Julia programming language and the CTO of JuliaHub. We start with the history of Julia and why it took a while to take off, the key principles behind the language, how it provides the speed of C with the ease of Python, and what it's been like running such a large open-source project. He sheds light on the original motivation for Julia, the process of creating it, and its involvement in AI.Hosted by David Mytton (Console) and Jean Yang (Akita Software).Things mentioned:"Telescoping Languages by Ken Kennedy"“Julia: Dynamism and Performance Reconciled by Design”Donald FischerChris Rackauckas: "A Julia Library for Neural Differential Equations"RR: Record and Replay FrameworkDell XPS laptop preloaded with UbuntuABOUT JEFF BEZANSONJeff Bezanson is one of the co-creators of the Julia programming language, along with Stefan Karpinski, Alan Edelman, and Viral B. Shah. He is also a co-founder of JuliaHub, a company that grew out of this project. He has a Ph.D. from MIT where he worked as a research scientist and he has authored a number of academic papers on the Julia language. The intention behind the creation of Julia was to establish a language that was both high-level and fast. His work on it has earned Jeff the J. H. Wilkinson Prize for Numerical Software.Highlights:[Jeff Bezanson]: You had to give up performance. That was just a law of the universe that they all learned. Then if you wanted performance, you had to use C or Fortran or something. This was just the way it was. I got introduced to that world of thinking in college and I thought it was really surprising because I knew that high-level languages could be fast. I knew there were good Lisp implementations, you had the ML family languages, there were really good high-level languages that had really, really good compilers and could be fast. And nobody seemed to be using them, which I just thought was amazing. I made it this mission to “Can we get all these people to realize that high-level languages can be fast, and they should be using a high-level language that's fast?” So [Julia] is my attempt to do that.— [0:02:59 - 0:03:44][Jeff Bezanson]: People have been trying to speed up dynamic languages of various kinds for a long time. That's been one of the long-running research threads in computer sciences, starting with a language like Smalltalk, for instance. How do you make it run fast? There's a whole zoo of both dynamic and static techniques. There are some really cool stuff people have invented to take these languages that you can't necessarily statically analyze using standard compiler techniques, and yet, nevertheless, generate fast code from them. It’s a fun game to play is how do we compile these languages that are not cooperative? So that makes it a challenge, which makes it a good research problem. But to me, it's kind of annoying because why do you always have to fight the language design? So instead, I approached it from the opposite direction and said, “All right. What are all the techniques that are known and available for doing this? Then how would you design a language to make those techniques work well?”— [0:13:18 - 0:14:12]Let us know what you think on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmyttonOr by email: hello@console.devAbout ConsoleConsole is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. Sign up for free at: https://console.dev
    続きを読む 一部表示
    32 分
  • WebAssembly, with Matt Butcher (Fermyon) - S04E08

    WebAssembly, with Matt Butcher (Fermyon) - S04E08
    2023/06/15
    In this episode, we speak with Matt Butcher, CEO at Fermyon. We discuss the four use cases for WebAssembly, why Wasm’s sandboxed approach is so secure, whether there's any danger retrofitting other use cases onto a language that was originally designed for the web, and how limitations like the lack of full networking support are going to be resolved.Hosted by David Mytton (Console) and Jean Yang (Akita Software).Things mentioned:OpenStackKubernetesDockerHelmThe Illustrated Children's Guide to KubernetesMicrosoftSingleStoreShopifyVMwareFermyon SpinFermyon CloudWizerwasm-optMacBook ProDell Ultrawide MonitoriPad ABOUT MATT BUTCHERMatt Butcher is the CEO of Fermyon. He is also a software engineer, tech author, speaker, and ex-professor. Formerly a principal software development engineer for Microsoft, he led a team of engineers that built open-source tools for cloud-native computing. They were responsible for Helm, Draft, OAM, Brigade, Krustlet, CNAB, Porter, Duffle, the VS Code Kubernetes Extension, and many others. Together with a team of 10 people from Deis Labs at Microsoft, he started Fermyon, a lighter, faster, and truly serverless cloud, architected to compile and ship code as Wasm binaries. Highlights:[Matt Butcher]: When Luke wrote his first blog post and said, “This is for a web browser,” it was built to not be particularly web-browser specific. It really just defined a machine code format in a way to execute that format. That was what kind of drew us to it as a technology. In the core WebAssembly 1.0 specification, there's nothing in there that binds you to a web browser environment, it’s just a straight-up runtime definition. So it was fairly easy to sort of pluck out a WebAssembly runtime and drop it somewhere else. In fact, there are several different WebAssembly runtimes that are not based on the browser at all. — [0:13:36 - 0:14:13][Matt Butcher]: If I were thinking about writing a new database, a new high-performance, multithreaded database, WebAssembly would not be the format I would target for this, right? Because there, you want to be able to do a lot of low-level management. Every little microsecond that you can tease out of IO and process manipulation is valuable. So I don't think we'll see those kinds of highly, highly IO-intensive tasks really land in WebAssembly for years because it's going to take the ecosystem a long time to really tune up and be fine-grained enough to deal with those things without compromising on security. It is possible that maybe never will we really want to write the kind of high-performance databases or high-performance number-crunching computing kinds of systems in WebAssembly. — [0:27:57 - 0:28:44] Let us know what you think on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmyttonOr by email: hello@console.devAbout ConsoleConsole is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. Sign up for free at: https://console.dev
    続きを読む 一部表示
    38 分
  • Why engineering sucks, with Eli Schleifer (Trunk) - S04E07

    Why engineering sucks, with Eli Schleifer (Trunk) - S04E07
    2023/06/08

    In this episode, we speak with Eli Schleifer, Co-CEO of Trunk. We discuss why engineering sucks, what developers can learn from how software gets built at Google and Uber, how individual developers can improve their coding experience, and why Git commit messages are useless.

    Hosted by David Mytton (Console) and Jean Yang (Akita Software).

    Things mentioned:

    • Mythical Man-Month
    • Google
    • Uber
    • BitTorrent
    • "Git commit messages are useless"
    • Warp
    • Slack
    • Linear
    • Visual Studio Code
    • MacBook Pro M1
       

    ABOUT ELI SCHLEIFER

    Eli Schleifer is the founder and co-CEO of Trunk, an all-in-one solution for scalably checking, testing, merging, and monitoring code. It helps developers write more secure code and ship faster to redefine software engineering at scale. He was previously a technical lead manager and a systems architect at Uber ATG, where he led the architecture and engineering of its self-driving platform. He also lead a team of engineers and technical leads in the development of multiple products under the YouTube Director umbrella and was a lead senior software development engineer at Microsoft.
     

    Highlights:

    [Eli Schleifer]: We should trust our engineers and also understand that code is constantly – it's a living document. It's changing all the time. If something gets in that's imperfect but not terrible, that's also okay. So if you have an engineer put up a pull request, you have feedback, leave that feedback and stamp the pull request. Assuming there's trust, then the engineer is going to follow up, fix up your comments, and then land that. There's no additional cycle. If you don't stamp it, that means you're going to— you’re basically saying to this person, “I'm going to hold up your work until you show me that you can actually follow through on the things I'm asking about.” That's a level of distrust that, I think, is not good in a highly collaborative working environment.

    — [0:15:48 - 0:16:28]


    [Eli Schleifer]: I think this is the biggest thing between a smaller startup and a giant tech company: At a giant tech company, at the end of the year, the giant tech company comes to the employee and is like, “Tell me what you did this year and why you have this job. Tell me all the good stuff you did for us.” At a smaller company, all management knows what all the people are actually doing for you. There’s a clear visibility into what those engineers are adding and contributing to the actual company's efforts. I think the biggest thing to focus on when it gets to 200 engineers or 2,000 is: what are these people actually working on? Who's making sure that there's a director of engineering for each of these smaller groups of 30, 40 people to make sure they're actually pushing towards something that matters, that matters to the company, that's going to move the needle? And that those engineers can still feel pride in and feel like they have impact?

    — [0:27:22 - 0:28:09]

     

    Let us know what you think on Twitter:

    https://twitter.com/consoledotdev

    https://twitter.com/davidmytton

    Or by email: hello@console.dev

    About Console

    Console is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. 

    Sign up for free at: https://console.dev
    続きを読む 一部表示
    37 分
  • Frontend platforms, with Matt Biilmann (Netlify) - S04E06

    Frontend platforms, with Matt Biilmann (Netlify) - S04E06
    2023/06/01

    In this episode, we speak with Matt Biilmann, CEO of Netlify. We discuss what it was like deploying code before Netlify, whether there is about to be a fragmentation in the JavaScript ecosystem as React gets more opinionated, where state and data fit into the Jamstack model, and how you might reach developers with a new project today. You’ll hear about the evolution of Netlify’s model, the Gatsby acquisition, and how Netlify has succeeded at staying on top of the fast-changing landscape.

    Hosted by David Mytton (Console) and Jean Yang (Akita Software).

    Things mentioned:

    • React
    • Shopify
    • Java
    • Gatsby
    • Next.js
    • WordPress
    • SolidJS
    • PlanetScale
    • Neon
    • Ruby on Rails
    • Astro
    • Mastodon
    • Nostr
    • MacBook
       

    ABOUT MATT BIILMANN

    Matt Biilmann is the CEO and Co-Founder of Netlify, a cloud platform that helps people build, deploy, and operate websites, web applications, and web stores swiftly and with ease. He has a long history of building DevTools, content management systems, and web infrastructure. Matt has been an active participant in open source and contributed to many well-known projects, including Ruby on Rails, JRuby, and Mongoid. Since launching its private beta back in March 2015, Netlify is now used by 3.5 million developers and is one of the fastest-growing web development platforms in the world.

    Highlights:

    Matt Biilmann: I really believed that we would move away from that model and move to a model where we would decouple the actual web experience layer into its own layer that web teams can build and deploy independently, and hopefully much faster. But I also saw at the time that there wasn't any tooling or infrastructure or workflows around that. So early on, when we started Netlify, there wasn't even a name for this web building. We had to come up with the term “Jamstack” to describe this idea of building the web experience layer on its own and typically seeing the backend split into all these different APIs and services, like all the headless CMSs that’s really become mainstream now.

    — [0:03:58 - 0:04:39]

     

    Matt Biilmann: Right now, what we're seeing happening around generative AI is probably going to change a lot of how we interface with computers over time, right? It’s already almost at the edge where you can imagine stitching a few tools together, and you would be having this kind of conversation with a program, rather than with a human. I think as that starts to happen, that will start to massively redefine how we consume content and commerce and so on. It will probably change a lot of what it means to build a website.

    — [0:17:09 - 0:17:41]

     

    Let us know what you think on Twitter:

    https://twitter.com/consoledotdev

    https://twitter.com/davidmytton

    Or by email: hello@console.dev

    About Console

    Console is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. 

    Sign up for free at: https://console.dev
    続きを読む 一部表示
    33 分
  • Devrel, with Christina Warren (GitHub) - S04E05

    Devrel, with Christina Warren (GitHub) - S04E05
    2023/05/25
    In this episode, we speak with Christina Warren, senior developer advocate at GitHub about all things Developer Relations (or “DevRel”). We talk about what constitutes a “typical day” in DevRel (if such a thing exists), how to get started in the field, and the types of skills needed. We also discuss how to measure success in DevRel, the importance of advocating for the user, and where exactly DevRel ends and product begins. You’ll hear about how Christina sees her role as a bridge between the community, product engineering, and the developers using the product, as well as where video fits into it all. Hosted by David Mytton (Console) and Jean Yang (Akita Software).Things mentioned:GitHubMicrosoftThe DownloadSouthern California Linux Expo / SCALELinuxAzureChatGPTChatGPT and Whisper APIsCommit AI2021 M1 MacBook Pro2020 iMac ABOUT CHRISTINA WARRENChristina Warren is a senior developer advocate at GitHub who works in DevRel, helping to connect GitHub’s developer community with its engineers. Prior to working for GitHub, she was a senior cloud developer advocate for Microsoft. With a background in journalism, she creates a lot of video content and is responsible for GitHub’s weekly YouTube show The Download, where she presents the week’s most insightful news for developers. You can find her on Twitter at @film_girl and on GitHub at @filmgirl.Highlights:Christina Warren: I think that developer relations should be part of product and engineering because it is a really core part of that. That said, to be successful, DevRel needs to be cross-functional so some companies have it under marketing. For their purposes, that might make sense. I think that it makes sense for it to be part of product and engineering. But I think that it's cross-functional insofar as I work with people on basically every different team at GitHub. That's one of the things that's great about GitHub is that they have a really good understanding and appreciation of the value that we can bring because we can help the product teams and the engineering teams create assets for their blog posts. We can help them with their message. We can highlight things because we are on the ground all the time. We can go, “Hey, hey. This thing happened and this is causing problems. Do we want to get ahead of this? And how can we make something better?”— [0:15:02 - 0:15:49]Christina Warren: The way I see my job — and I can't say this for every person in DevRel — but the way I see my job is my title is “developer advocate”, but I'm not advocating for GitHub. I'm advocating for GitHub’s users. I'm advocating for our community. That's really what I'm trying to do. Because I think that by advocating for them, that's how GitHub can be most successful. But, of course, not everybody and not every company might see it that way. They might see it as, “Oh, your only job is just to praise and talk about how great we are.” I don't see it that way. I think that to be really successful, you need to be transparent, you need to be honest, you need to be authentic. That includes when there are situations where you might screw up or when things might not be right because I think that that's what builds trust.— [0:16:24 - 0:17:07]Let us know what you think on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmyttonhttps://twitter.com/jeanqasaurOr by email: hello@console.devAbout ConsoleConsole is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. Sign up for free at: https://console.dev
    続きを読む 一部表示
    37 分
  • Shell scripting, with Steve Lee (Microsoft) - S04E04

    Shell scripting, with Steve Lee (Microsoft) - S04E04
    2023/05/18
    In this episode, we speak with Steve Lee, principal software engineer manager on the PowerShell team at Microsoft. We start with what PowerShell is and why its object-based approach is interesting, then get into what it was like open sourcing a project at Microsoft back in 2016. We discuss the transition to using GitHub and what it's like managing an open source project at scale, bouncing community with features, bugs, and requests from users, alongside Microsoft’s goals. We also talk about PowerShell and its relation to AI, before we get some insight into what we can expect from it in the near future.  Things mentioned:MicrosoftPowerShellOpenSSHUnixLinuxWMIWinRMDMTFPhysical Computer System ViewWS-ManAzure.NetPowerShell GalleryVisual StudioPythonGitHubPesterChatGPTDoug FinkeVisual Studio CodePowerShell Team blogABOUT STEVE LEE.Steve Lee is the principal software engineer manager on the PowerShell team at Microsoft. He’s been with the company since 2000 when he started out working on Internet Explorer for Unix. More recently, his team was responsible for PowerShell Core 6, the open-source cross-platform (Windows, Linux, macOS) version of the object-oriented scripting and interactive shell, developed on GitHub.   Highlights:Steve Lee: I think the way we position PowerShell, it’s really a ‘glue language’, and not intended for developing full applications. Now, I do know that there are folks in the community who built very complex systems on PowerShell script and we’ll support them by all means, but it's not intended for that purpose. It’s really for— What we use within our team is really like, you're trying to test out some new .Net API. It's actually much faster to write it in PowerShell script with a few lines of code than running C# that you would have to compile and do that work. So it makes it very easy to test out new things, prototyping before you commit to writing critical proper development code.— [0:08:46 - 0:09:22]Steve Lee: Everyone probably saw how Bing and ChatGPT has integration. So that’s something— AI is on top of everyone's mind. And that is something that we've actually been looking at for a while. So I'm not sure if anyone is aware but, we had — even before ChatGPT, even before some other popup ones that came out, like Stable Diffusion and stuff like that — we were looking at AI several years ago before things were ready. And we actually have a plug-in model. So PSReadLine is a model that we use as the way to present the interactive experience for PowerShell users. And so one thing that we did back in, I think 7.1 — which should have been probably, what, two, three years ago — is we added a predictor plugin, so someone could actually build a predictor in C# and be able to present that through PSReadLine to the user.— [0:27:27 - 0:28:13]  Let us know what you think on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmyttonhttps://twitter.com/jeanqasaurOr by email: hello@console.devAbout ConsoleConsole is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don’t have to. Sign up for free at: https://console.dev
    続きを読む 一部表示
    32 分