text stringlengths 0 2.29k |
|---|
Essentially, given that our society is facing, or like humanity is facing very significant existential threats, to actually reduce the stakes of a lot of the decisions. Like, it's not like "Oh, we need to go to Mars!" We don't need these -- like, we can survive here at least for another, let's say, 100,000 years. You t... |
I think there's no single lambda function invocation that's going to justify Rust. But tens of billions or trillions of invocations - at that sort of scale, things change. And, again, I kind of want to stress that we have problems which are solvable, but they aren't going to be solved with expecting some government or ... |
**Gerhard Lazu:** This sounds like a great takeaway to me, Tim. I was going to ask you what would be your key takeaway, but this sounds like it. Well, you made me definitely think -- I'm not sure about the clicking part. We'll see what clicks. But you made me think. I'm looking forward to you getting on your bike, and ... |
**Tim McNamara:** I think it's actually the 17th... |
**Gerhard Lazu:** Rust Nation UK... 16th and 17th of February. So - I mean, it's at the Brewery. Oh yeah, that's a good place in London. Now, I think this episode will come out around the 15th, so there won't be a lot of time for you to listen to it and join the conference... But just in case you are, we had the confer... |
**Tim McNamara:** Yeah, me too. Absolutely. It's gonna be fun, whatever it is. |
**Gerhard Lazu:** Until next time. |
**Tim McNamara:** Take care. Bye-bye. |
• Play With Go was created as an open-source project to showcase specific use cases of the Go programming language |
• Marcos Nils worked with Paul Jolly to develop Play With Go, building on his experience with Play With Docker |
• The idea for Play With Go came from a need in the Go community to demonstrate tooling and module management concepts |
• Play With Go has received positive feedback and has been used by many people, but development activity has slowed down recently |
• Marcos Nils started Play With Docker after attending an event where he saw a need for a simpler way to showcase Docker use cases |
• The idea for Play With Docker came from attending the Docker Contributors Summit and seeing attendees struggling with complex tasks during Jérôme Petazzoni's training |
• Play With Docker was initially developed as a minimal proof-of-concept and eventually grew into a more comprehensive tool |
• The concept of platform engineering and its goals, with Marcos defining it as making developers' lives easier |
• Comparison between platform engineering and DevOps, with discussions on who owns platform engineering and how it fits into existing teams |
• The difference between platform engineering and DevOps, with Marcos stating that they are not mutually exclusive but rather complementary |
• Challenges in implementing platform engineering, including the need for a framework where everyone can contribute to building faster, more secure software |
• The importance of understanding users' pain points and iterating on solutions in platform engineering |
• DevOps teams often overlap with other teams, such as SREs, due to unclear metrics and goals. |
• Platforms can help frame and connect different teams' goals, but do not solve underlying issues. |
• The concept of platforms has been around for a long time, even before eight years ago. |
• A company's context and infrastructure can greatly impact the success or failure of a platform. |
• Principles such as autonomy, golden paths, and health checks have remained relatively consistent over time despite changes in technology. |
• The basics of platform development, including scripts and workflows, have also stayed similar despite advancements in technology. |
• One potential area for improvement is reducing the complexity and overhead of building and managing platforms. |
• Challenges of building distributed systems and managed services |
• Trying to replicate cloud services in-house (e.g. BQ as SQS alternative) |
• Scaling issues and need for redoing work |
• Risks of adopting new technologies before they are mature (e.g. Node.js 0.4) |
• Importance of simplicity when designing complex systems |
• Difficulty of building stateful services and distributed systems |
• Examples of production data-related problems (e.g. RabbitMQ, queuing) |
• Consequences of system downtime (e.g. payroll issues, customer impact) |
• Building a distributed caching system with Redis compatibility |
• Memory leak issue in caching library used |
• Experience bootstrapping a startup with little knowledge of cloud and distributed systems |
• Development of early platforms for AI engineers |
• Use of Docker, AWS, and Amazon services for orchestration and deployment |
• Simplification of workflow for developers through minimal descriptors (Docker files) |
• Early stages of platform engineering, influenced by companies like Heroku and the CNCF |
• Stateful data problem and management in cloud-based platforms |
• Development of a service to handle model state in AI applications |
• Last platform mentioned: Wildlife Studios, a gaming company with experience in mobile game development |
• Context is crucial when building a platform for software engineers |
• Developers were already exposed to Kubernetes and had a workflow in place |
• A new VP introduced an idea to build a centralized UI and control plane like in their previous company, but it didn't fit the current organization and workflows |
• The team adopted Backstage, a developer portal that was designed for a specific type of organization, which led to a complex and resource-intensive project |
• It's better to start small and iterate on existing workflows rather than introducing an out-of-the-shelf platform or building a new one from scratch |
• Big bang rewrites are considered a bad idea due to unknown risks and potential for introducing new problems. |
• Incremental changes and data-driven decision making are preferred over large-scale platform implementations. |
• Centralized visualization and communication platforms can simplify development and augment team collaboration. |
• Starting with smaller, more manageable projects and building on existing infrastructure is suggested instead of starting from scratch. |
• Serverless and containerization options are being considered, but serverless has limitations due to unresolved issues such as persistent database management. |
• Discussing serverless computing and its potential disruption of traditional app development |
• Comparison of Kubernetes to other platforms, with doubts about its suitability for serverless workloads |
• Preview of upcoming trends and technologies in 2023, including WASM and serverless adoption |
• Desire for more human connection and community sharing in the tech industry |
• Personal reflection on past year's events and future collaborations |
**Gerhard Lazu:** Hey, Marcos. How's it going? |
**Marcos Nils:** Hey, Gerhard. Doing great. It's a sunny day here in Punta del Este, Uruguay, and I'm really happy to be here with you to chat about technology, life, and whatever comes up. |
**Gerhard Lazu:** Yeah, welcome to Ship It. It's been a long time coming. I'm so glad that we're finally doing this. |
**Marcos Nils:** It's great. I think this is the first time that I've been on the show, right? |
**Gerhard Lazu:** The first time, yes. Not the last time. I'm sure it's not the last time... Well, I say that; it depends how it goes. \[laughs\] |
**Marcos Nils:** It really depends. Yeah, so let's see if we can get some interest from the audience and make this episode like something for people to take with them. |
**Gerhard Lazu:** So the first thing which I want to say is thank you for Play With Go. |
**Marcos Nils:** Oh, my pressure. |
**Gerhard Lazu:** What made you build it? |
**Marcos Nils:** First of all, it's a joint effort. These things are difficult to build by just one person, so I would like to congratulate and basically celebrate it with the other authors of the Playground. There's one person which I started the whole Play With series thing, which is called Jonathan. We are colleague... |
So yeah, it's a fun story, because we met in London... I actually went to the Go meet-up there in 2018 or '19, I think. I can recall exactly... And he was presenting something around learning Go. I think the brand new go.dev domain was also published there, with Carmen showcasing it. I had a history of making Play With... |
**Gerhard Lazu:** And what happened afterwards? What happened after you got it out there? |
**Marcos Nils:** Basically, the reception was pretty nice from people using it. I guess what I take with me of that experience is that I learned a lot during that process. First of all, I met people around the project; I think that's what I like the most of doing open source, is the people around it. And I had the expe... |
So it's been great. I mean, I have to agree that it's been quite stale for the past couple of months, I would say, this year... But we are looking for contributors, or like people that want to showcase different Go use cases... There's the new Workspaces thing that we would like to include as well. But yeah, we're look... |
**Gerhard Lazu:** So while I have used Play With Go and multiple times, and I've found it super-useful - again, thank you very much for that. And I really mean it. It's been so easy, so easy, especially when it comes to sharing with others. This is it. Super-simple. I know that you started with Play With Docker; that w... |
**Marcos Nils:** \[06:10\] That's a really funny story... I don't know if I would state it as an example. Maybe it will, but... We were in Berlin actually, with Jonathan, the person that I mentioned before, which was someone that I was working with at the time... And we were attending an event that was called Docker Co... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.