elguyosupremo's comments

We use GCP Cloud Build for most of our CI needs, and then Argo and Kargo to deploy things.

Cloud Build is generally pretty straight forward to use and we rarely have to mess with pipelines after initial setup. It's easy to make new images with any tools you need for your build process.

Triggers and repo connections are a little annoying to setup, but if you get a little terraform module set up it's not too bad.

They're owned by Mercedes, I'm sure they probably have access to the capital they need.

Perhaps in contrast the president of Princeton was a Rhodes scholar and clerked for a Supreme Court justice before going to teaching and administration.

Establishing a legal route to train LLMs on copywriten content could certainly have a chilling affect on the progress of science and useful arts... Why would someone devote their life to their studies or craft when they know that an LLM will hoover it up and start plagiarizing it immediately?

This was announced in April, and this is the second time in two days I've seen people reposting it. What gives?

Sure they do, Ford released the 2022 Fords the year after the 2021s.

New York State does not require permits for long guns, NYC has more stringent licensing though.

Search for "all quotas" in the GCP console, from there you can view all your quotas and request increases.

And even if I can get what I need via CLI it's nice that higher level people in the org can click around and get what they need without having to bother me to retrieve the data for them.

family farm becomes a different thing when you start milking 1100 cows, it's usually a few of the family working with several undocumented immigrants. I live in upstate NY also tho our family sold the farm a couple of decades ago.

The farm we used to own has gone towards organic milk to get a premium for their product, and the family that bought it now relies heavily on undocumented immigrants.

https://amsaw.org/amsaw-ithappenedinhistory-092503-faulkner.... may be what you are looking for.

``` He wrote all of his books in longhand, often struggling with words and definitions. He didn't own a dictionary. Often, he would make up his own words to suit the moment, combine two words into one, or turn nouns into verbs and vice versa. If he couldn't spell something, he would walk down to the local drugstore and ask someone there to look it up for him. Sometimes, he would stop people on the street and ask them for the meaning of a word. "I'm looking for a word. It means the same as 'running fast' but I don't want to use 'running fast.'" ```

Supposing cell towers don't currently have a key; if they did your cell provider would certainly have a way to push new ones to your phone, and under government warrant they'd simply push the key of the stingray to your phone as well, or give the stingray the key of an existing tower.

This is one of the reasons I have become an advocate for mob programming, I think it allows people to have a best-of-both-worlds kind of experience; allowing the flexibility of remote work while facilitating the direct collaboration of in-person work.

I don't think it scales much beyond 4-6 developers, if you have bigger teams than that you could try a couple of sub-mobs.

I was really skeptical at first, but we've been doing it for over a year now and I've come to thoroughly enjoy it. I find that I get stuck on issues much less frequently because I have other people to talk through them, knowledge transfer is inherent, and when you have multiple people writing and reviewing the code as it's written PR reviews become basically instant and you can deploy much faster.

I've found it to be quite the opposite. It's also important to note that mob programming recommends rotating who is "driving" the session, so we change who is sharing every 15 minutes.

I don't think this approach scales to more than a team of 4-6 people but we've been able to forge strong bonds on our team, solve complex problems (in domain definition, actual code, ci/cd issues, and more) in ways that the entire team feels are appropriate and while also keeping the whole team abreast of all the changes. We get far more done than we used to and we've successfully onboarded several new team members.

This piece goes from talking about meta layoffs to an indictment of remote work surprisingly quick.

I love remote work, because I grew up in a small city with no companies operating in my industry and when covid hit I was able to go full remote, move back home, and be around my friends and family while contributing to my company and to my local economy.

The biggest thing that has helped my dev team thrive and be able to onboard new members is mob programming (https://en.wikipedia.org/wiki/Mob_programming). We have our own take on exactly how we do it, but the gist is that all our software engineers are in a video conference with each other as much as possible and focus on a single task.

We're starting to add new members in timezones that are 5+ hours offset from the rest of the team and that integration is proving to be hard. If anyone has advice on building TZ-distributed teams I would love to hear advice!

The thing I don't get about this concept is what about heavy industries, how do all the employees of a shipyard live within 15 minutes of it while still allowing room for all the people that support the shipwrights? It doesn't sound like a threat to civil liberties, it sounds like an agrarian, luddite pipe dream.

The source was posted 4 days ago, I wonder if they changed things since then, but I agree the screenshots you posted seem pretty Normal. And that's depressing because a $110 surcharge on each ticket being normal sucks.

I think short-term rental rules really need to be determined on a community by community basis. In some places (like beach towns, or ski resorts) it might be ok to have 50% (just pulling that number out of nowhere) houses be short-term rentals. In NYC or San Francisco it might make more sense to limit short-term rentals more (a certain number of nights per unit per year), the policing of such a policy though, oi!