Not sure what my point is here tbh. The internet sucks and I don't have a solution

Only laws (accommodate EVs and/or WFH) or spending time sitting at a gas station will help me here. No landlord is interested in accommodating an EV unless it's a net benefit to them (and thus a net negative to me, who already spends 40% income just to have a place to work.)

We've been doing this for a long time at my current workplace (for dev containers) and haven't run into any problems.

Actually in the same comment I replied to, but there doesn't seem to be a way to edit posts in my mobile client.

Can you expand on this? I read the linked doc, and it looked like a separate API should be used to used to "persist a network connection" (my words), but as someone with no Android dev experience there don't seem to be any obvious limitations.

You did mention in another reply that only certain root apps can do [what we expect]. Is there a link where I can learn more about that?

> You can instantly connect using Google Circle to Search or Google Lens.

Is there something special about the Google integrations that other apps can't achieve (I'm not an Android developer)?

I don't think we were really taught at all about European/Asian history or the Soviet Union. I think I could have taken some classes related to those in highschool (secondary school), but for anyone working towards a non-history bachelor's degree those courses were generally not something that you could fit in your timetable.

This is split over hundreds of microservice repositories, each of which maintains its own Terraform.

We don't read state from other Terraform deployments, and use published reusable modules when convenient and a tfvars file for every deployment.

At this point I can't imagine doing Terraform any other way.

I would be more inclined to blame this on Apple than Docker, but I haven't looked too deeply since things are working for us. Curious about you folks' opinions.

Definitely worth a watch if you're interested in Scrabble at all: https://www.youtube.com/watch?v=6RvNxkQ6Bgs

This is fine until you're working with hundreds of other developers. I believe the reason solutions like this exist is to abstract git away from most devs, because in (my experience) many enterprise devs have only rudimentary git knowledge.

Sure, the devs should "just learn git" - but the same argument applies to a lot of other tech nowadays. Ultimately most folks seem to want to close their ticket off and move to the next one.

Git submodules and git subtrees generally do not fit my org's needs - we have internal tooling similar to this. Happy to expand on that if you have questions.

I'm tired of slow, risky, late-night upgrades to the appliance. I'm tired of sending support bundles and being told to run a customized string of MySQL commands to resolve peculiar issues. I'm tired of checking the roadmap and telling folks "yes, they announced that feature, but it won't be available to us for at least 12 months." I'm tired of a feature eventually being in the GHES release notes, only for GitHub to have made a mistake and it not be available for another two versions.

We're moving to GHEC. I'm concerned about the semi-frequent outages there, but we're not running HA GHES so it has become a liability for us.