Live data from Hacker News

Using Apple Silicon (M1) as a cloud engineer, two months in

blog.earthly.dev

1–10 of 103 posts

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#2
Git going missing is likely to do with macOS updates. Since Apple moved to sealed system partition and "non-diff" os updates, each OS update comes as a unified whole package (often sized in the multiple gigs of data)

This wipes out the xcode-select installed git (because instead of "patching" the existing system, it just replaces the whole lot of it with whatever is in the archive). It leaves xcode alone (since that's in the Application folder), but any additional xcode command line tools gets wiped out by the OS update, and the system needs that reinstalled.

I ran into this with Intel based Macs running the beta 11.3 as well, so it's not necessarily an M1 issue.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#4

Git going missing is likely to do with macOS updates. Since Apple moved to sealed system partition and "non-diff" os updates, each OS update comes as a unified whole package (often sized in the multiple gigs of data) This wipes out the xcode-select installed git (because instead of "patching" the existing system, it just replaces the whole lot of it with whatever is in the archive). It leaves xcode alone (since that'…

I wonder if it might be time to shift the majority of package installations to user-local. Outside of things where system-level is unavoidable (e.g. kexts) are there good reasons not to?

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#6
Love my M1, but a heads up – if you're dependent on Postgres-based tests running inside of Docker (quite a common usecase!) the performance is completely unusable still:

https://github.com/docker/for-mac/issues/5236

We're talking a suite that normally takes 30 seconds taking 10+ minutes.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#9
post #8

yes cloud engineer yes front end engineer yes senior software cloud dev potato computer engineer yes architectural neural network cloud potato software enterprise senior architect engineer what does cloud engineer even mean?

It's a kind of developer and operations role that focuses on cloud technologies, typically the big three (AWS/GCP/Azure).

Why? Do you care or are you just making fun of the job title? If someone wrote "as a Windows Engineer" would you have scoffed?

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#10
post #8

yes cloud engineer yes front end engineer yes senior software cloud dev potato computer engineer yes architectural neural network cloud potato software enterprise senior architect engineer what does cloud engineer even mean?

It's a kind of developer and operations role that focuses on cloud technologies, typically the big three (AWS/GCP/Azure). Why? Do you care or are you just making fun of the job title? If someone wrote "as a Windows Engineer" would you have scoffed?

Some software engineers don't know how job roles are named everywhere else. They think it's all just Software Engineer I or II, whatever that's supposed to represent or what their job entails.

Meanwhile, EEs split their roles: Verification Engineers, Hardware Engineers, Power Engineers, QA Engineers. It's straight, well defined and provides a structure. The fact that people mock this is why software quality is looked down upon.

Post reply on HN