That is the wrong way to look at it.

If this requirement was in place they would be a bit more careful about terminating accounts because the cost equation would incentivize it. Maybe they would be more careful in their automation or require more than one level of human review before cutting off access.

These companies are gatekeepers for their platform. It isn’t crazy to require them to act more responsibly.

Apple is in the process of fixing Tahoe which was a regression from Sequoia the previous release. Tahoe is decent with 26.4 though from what I am hearing. Either OS version is far far better than regular Windows 11 though.

Apple’s real differentiator is their silicon. M series chips are just incredibly good and you get a full workday out of them on battery.

The M1 Pro I still have at work is easily the best laptop I have ever used. For side projects I use an M4 air with maxed out RAM and it has no issues with anything I have thrown at it.

I'm also still on my M1 and I just don't see a need to upgrade. I've never owned a laptop this long without even considering getting a new one. It's still so fast, so cool, great screen, biometric unlocking... it's just incredible.

I have seen this mostly on teams which refuse to formalize preferences into a style guide.

I have fixed this by forcing the issue and we get together as a team, set a standard and document it. If we can use tools to enforce it automatically we do that. If not you get a comment with a link to the style guide and told to fix it.

Style is subjective but consistency is not. Having a formal style guide which is automatically enforced helps with onboarding and code review as well.

Hard agree here. I think the best predictor of whether someone will be good, eventually, at something is “do they love it”. If they do then chances are they will spend lots of focused time practicing and actively seeking out ways to get better.

Maybe that love, or at least liking something, comes from inherent talent to some degree but all the talent in the world won’t help you if you don’t put in the time.

I use an M4 air with maxed out RAM for software development and it has no issues.

I think you might have a bad one. See if support will do anything for you this is not normal.

Yep getting 500 errors intermittently on fetch and checkout operations in my CI pretty consistently at the moment. Like 1 in 2 attempts

What I am excited about is the possibility of LLMs to draw conclusions from the last 150years of scientific papers.

There have been lots of instances of knowledge being rediscovered even when it was previously published but sitting on some shelf forgotten. LLMs ability to digest large volumes of data will I think help with this issue.

We will still need to reproduce and verify conclusions but will be interesting to see what might come from this.

Returning an empty result in that case may cause a more subtle failure. I would think returning an error would be a bit better as it would clearly communicate that the caller called the API endpoint incorrectly. If it’s HTTP a 400 Bad Request status code would seem appropriate.

If you look at what $50 a month gets you at OVH or Hetzner then their post makes more sense.

It isn’t an apples to apples comparison. But, you trade some additional operational overhead for a whole lot more hardware.

Totally agree - I was just trying to give a perspective for the user scale figures

Probably, which is unfortunate. I have personally seen a VP be shocked that morale tanked after a large layoff. I think he said “you would think they would be happy they still have jobs”. Lots of sociopaths in the C-Suite.