This no-code approach is a game-changer for teams without DevOps experts, super impressed!

Very interesting interview. Thank you.

interesting conversation really good idea about the complexity in flexibility sometimes we also write code just for our entertainment which generates chaos, partially for the functionality

Nobody is kind of a stretch i cN list many who need gpus that are not gamers

Great episode! I loved hearing the story behind the project/product. I wish the renovate team continued success in the future with your sincere open source.

I think the difference between labels and types is kind of like a type... you get one specific type that you can set, but labels are like tags... you can reuse them and perhaps there is less consequence if it is mislabeled. Like if you want to use a workflow to handle something of importance, the type would be the more "reliable" meschanism that you can perhaps have more controls over. Whereas labels are free-form and anybody can set anything as a label.

Thanks guys!

Also Akuity’s Kargo reached v1.0 this week, I’d love to get your thoughts on that 🙏

Please consider reviewing this year’s thoughtworks radar report, in tomorrow live session

So… Nushell is Powershell?

I love that the intro counter is cut 😅

9:50 Notorious patent trolls SCO Group bought SCO UNIX from the Santa Cruz Operation company, perhaps that’s who you’re thinking of?

That was a weird end of the show. A bit rough? LGTM is the Grafana stack for obs: Loki Grafana Tempo Mimir

and please please you must never change the pronounciation for those annoying americans who moans and complains. for myself, i shall always be saying it the proper way, which is rusk in solidarity with my european friends. this more interesting newer language, it is definately rusk very grateful for this is very much appreciated victor. indeed and genuinely so. made my day! 🖤

very grateful of the youtube auto translate here... since whenever victor refers to his new programming language, and the spanish accent since google gives me the subtitles translation "rusk" language. just whenever victor mentions "rusk" our teacher now i am very grateful learning from victor to be saying "rusk" nowadays. whenever people is talking about the different programming languages. then shall always be sure to tell them about this new rusk one. (so just in case they never heard it before). everybody

I completely agree with the sentiment, to a great extent. “From scratch” doesn’t mean going back to the beginning of time, though. It is a cooking term and in that context, the cook doesn’t grow the grain or mill it. Also, it never means abandoning previous knowledge. However, “first principles” is a thing.

Ansible needs to be folded in under the Hashi tool stack. Maybe even rewrite it to use HCL2, as an option... in Go, instead of Python. Then work towards better integrations... and have an HCP Ansible with a SaaS version of Ansible Automation Platform... then rename AAP to Ansible Enterprise.

Accents are experiencing the same thing

Easy way to handle Terraform state... use a location for state storage that implements state locking. Problem solved.

Guys you're back! I missed you!

When is the next live Friday show?

Most people are poor at thinking about a problem, and quickly start solutionizing. They don't know how to clarify a problem. For example, what's the purpose of the Three Char's to the file extension. What are they going to do with it. What's the goal. People (managers/Directors) think they should go to developers with a solution. However, 10 developers can solve a problem in a more robust way that also uphold all existing business logic if they are given a problem and not a solution. "maybe the problem is not the problem" has the root cause in lack of experience within the business, process, people and systems. It takes time to educate 10 developers, 2 product owners and 4 testers about a "problem", so giving them a solution, is quicker.. Or is it....

I've seen this issue too, so many times almost 30 years of software and architecture consulting🙂I had something similar a couple of months ago, Task: provide an API (X), using REST (Y), for a complex business model. After a couple of weeks I realized that the complexity of satisfying all the service clients with REST calls was going to be a huge undertaking. I told the project management that we are switching to GraphQL (new Y to solve X) and leave the "required data" to the calling services and not trying to implement an endpoint for each use case.

Super interesting! I never considered using k8s purely for control of external applications. How do you ensure tight coupling and feedback in this pattern?

Sil. Break it down for them. What two businesses have been recession proof since time immemorial

Devbox works wonderfully under Ubuntu Linux. I haven't tried installing global packages using it yet. I am still debating whether or not to make the plunge into NixOS as a main Linux distro.

Eivissa the tiny island outside spain is Ibiza. The nr1 party island in the world and yo have definitly heard about that one or you have been living under a rock :D. Great podcast and keep up the great work, really appreciate them ♥

❤

I see DSL as "Domain Specific Language" but "Domain Structured Language" is a new creature. Apart from that, let us go through SGML, XML JSON and YAML. IMHO, describing your "DSL" mostly needs a "DSL" 😜

Why not chatgpt?

@24:26 asking about directory automation - direnv can handle that - you can create an .envrc script and add any shell commands you want to run.

As a developer-turned-DevOps-turned-Cloud Architect who is currently doing a multi-cloud adoption project and dealing with operationalization in a risk adverse SMB...I think this might be the most targeted podcast I've ever listened to. Looks like I also need to dive into Cilium a bit to understand the feature-parity comment that Ádám mentioned.

i thought I'm the only one who plays steam deck in teams meetings.

0:21 who is Taylor Swift ? 🤣🤣

Interesting podcast on Platfrom Engineering, my view point is why we don't like abstractions anymore, why everyone has to know everything. AWS Architects, DevSecOps, Developers, Integration Architects everyone needs to know everything to solve an issue of why Service A cannot connect to Service B in a different AWS Account which goes through 10's of hops through so many services to just send a JSON payload.

Thanks 👍

Hey guys! Been loving the content, thanks for all the lessons

AI has been around since the 1950s. Yes, it’s generally available now, but can we really expect it to evolve as much as people are saying in, let’s say, 5 years from now? It will definitely enter different industries, but I sense it won’t evolve as much as we believe. I love it and embrace it, but is the pace at which it evolves that high? If I compare it to a year ago, it hasn’t evolved that much, except there are more domains it has penetrated.

Thanks for mentioning Pulumi!

Is there a Packer alternative? I haven’t found one yet as an equivalent.

OpenBao is the vault fork. By IBM employees lol

As Hashicorp wise I agree they’ll go full proprietary just like RHEL

Google does try to be the cloud of the clouds. A lot of multi cloud management features. GKEE, SCC enterprise, BigQuery Omni, AlloyDB Omni. List goes on

IBM now owns Hashicorp. Let’s see how it goes

Congratulations Darin!!

Not helpful

Thanks

I wish we could plug in different terminals into VS Code.

Can't describe it better

This topic is relevant every day for me . I oversee infrastructure on AWS/EKS, while a parallel team manages the same product with same set microservice on GCP/GKE. It's worth watching and checking out the article.