Wow, no, no connection! I need to read this book now so I can read about my cat!

What do you mean?

the needs are pretty special

“Epic judge”?

Thank you for sharing such a tender and adorable part of your life!

YAML works great for small config files, or situations where your configuration is fully declarative. Go look at the Kubernetes API with its resources.

People think YAML sucks because everyone loves creating spaghetti config/templates with it.

One reason it tends to become an absolute unholy mess is because people work around the declarative nature of those APIs by shoving imperative code into it. Think complicated Helm charts with little snippets of logic and code all over the place. It just isn’t really made for doing that.

It also forces your brain to switch back and forth between the two different paradigms. It doesn’t just become hard to read, it becomes hard to reason about.

I was hoping for a Martian dating sim from the name.

Played through 64 a few years ago, still holds up great.

I should really play Legends 2.

This is RPS’s style, you don’t have to like it but it definitely fits in.

Sometimes you just need to get yourself into it to survive

I decided to read through their “about us” page and this just isn’t true, unless he is using a pseudonym and lying about all of the other writers/researchers.

I have configured systems like Okta and this detail almost makes me believe this is a real leak. 😂

I doubt he trained for that long if he left the chinstrap unbuckled

adamsandlering

Disagree, I really needed it.

Thank you!

I set up a monorepo that had a library used by several different projects. It was my first foray into DevOps and we had this problem.

I decided to version and release the library whenever a change was merged to it on the trunk. Other projects would depend on one of those versions and could be updated at their own pace. There was a lot of hidden complexity and many gotchas so we needed some rules to make it functional. It worked good once those were sorted out.

One rule we needed was that changes to the library had to be merged and released prior to any downstream project that relied on those changes. This made a lot of sense from certain perspectives but it was annoying developers. They couldn’t simply open a single PR containing both changes. This had a huge positive impact on the codebase over time IMO but that’s a different story.

How is it done at Meta? Always compile and depend on latest? Is the library copied into different projects, or did you just mean you had to update several projects whenever the library’s interfaces changed?

Most of the food in the area of Spain I visited (South) was bad because it was made for British tourists. Had no idea it was going to be like that.

Gibraltar was cool despite being even more British.

On the other hand, using ChatGPT for your Lemmy comments sticks out like a sore thumb

ZA PAPER