thtmnisamnstr

The general rule to follow is that you need as much VRAM as the model size. 30b models are usually around 19GB. So, most likely a GPU with 24GB of VRAM.

Gemini CLI is a solid alternative to Claude Code. The limits are restrictive, though. If you're paying for Max, I can't imagine Gemini CLI will take you very far.

1. Unlike most developed countries, in India (and many other develping countries), people in authority are expected to be respected unconditinally(almost). Questioning a manager, teacher, or senior is often seen as disrespect or incompetence. So, instead of asking for clarification, many people just "do something" and hope it is acceptable. You can think of this as a lighter version of Japanese office culture, but not limited to office... it's kind of everywhere in society.

I was a manager at Deloitte in their tech consulting practice. I led fairly large teams of devs based in India. This is very true, and it takes a lot of time and trust-building to overcome. Making Indian devs, especially early-career ones, comfortable enough to oppose something or offer feedback is non-trivial, and often Indian engineering managers make it more difficult. Overcoming cultural hierarchy is hard.

Uncertainty is frequently a contributor to depression. Uncertainty is one of the most reliable stress triggers, which, over prolonged periods of time, especially when paired with low perceived control, is a direct path to increased depression. So if something is uncertain, it is often depressing as well.

What they are describing sounds like the Glove80. I've been using the Glove80 for a year, and I'm a huge fan of it. Took a while to get used to, but now typing is way more comfortable than it was on even my old Freestyle Kinesis.

I'm a marketer. I write a lot. GPT-4.5 is really good at natural sounding writing. It's nearing the point where it would be worth $200/mth for me to have access to it all the time.

Can't you still use the European site to download the EOS Webcam Utility for free? https://www.canon-europe.com/cameras/eos-webcam-utility/

You could have solved this issue. Your coding fingers turned into complaining fingers. If you really had a problem, you should have opened a PR with a license instead of demanding that OP do it on your timeline.

I'd dispute that. No gi is not easier on the knees, ankles, or shoulders IMO. The slipperiness compared to gi comes with the downside of sudden slipping movements that put your knees and shoulders at higher risk of injury and dislocation. The increased focus on leg attacks also puts your knees and ankles at higher risk. Add to that the seeming slant towards more explosive movements in no gi, and the overall risk of injury should be higher than gi. You likely see more injuries in gi, because way more people train gi than no gi still.

Note: I train gi and no gi and have been for almost 10 years. My biggest injury happened in the gi (broken hand), but I've had significantly more ankle and knee sprains and shoulder dislocations in no gi. Also, the morning after no gi feels like I got hit by a truck compared to the morning after gi.

I work at Earthly. We build a pretty popular open source build tool. I've worked for several companies that build OSS before Earthly as well.

At Earthly, a few years ago, the founder and CEO had these same concerns about big cloud providers and switched to a source available license. There was backlash, and after around a year, we switched back to open source. We've discussed things like this a lot, and believe an open source license is best for our product, our users, and our business.

The way that we differ from Hashicorp, Redis, and others that have switched to source available licenses is that the service we offer and generate revenue from isn't just a hosted version of our OSS. It's several services that natively integrate with our OSS but are not open source. This seems like one of the only ways a company that maintains popular OSS can survive without switching licenses: build great OSS that users love, build non-OSS services that integrate with and augment your OSS (and/or open up new use cases), and charge for those services.

If the service a company sells is just a hosted version of their OSS, even if it has a bunch of non-OSS bells and whistles added on, that company is at risk of a cloud provider eating their lunch unless they switch to a non-OSS license.

How old do you think the author is? He’s not some “new generation” dev.

Thanks for posting. I’m the author of this post. If you have any questions about Earthly, Earthly Satellites, or Self-Hosted Satellites, I’m happy to answer.

This one is ridiculous. This should already exist. Until GitHub builds it, you can use GitHub Actions to kick your builds off but run them remotely on Earthly Cloud (https://earthly.dev/). Even the free tier includes arm64 remote runners.

Note: I work at Earthly, but I'm not wrong about this being a good, free, arm64-native workflow for GitHub Actions.

I got fired up writing this one. Can’t stand the way McKinsey abuses DORA in that new report.

You should sit down with the OP and author of this article, Adam. He has a really good podcast called Corecursive, and your story seems right in its wheelhouse.

Did you use nixos for builds or as your daily driver (or both)? Using nixos as a daily driver doesn't make sense to me, but I'm probably missing something.

You've probably heard about this before and didn't realize it. Did you watch Training Day? That whole movie was centered around the leader of a cop gang.

Docker on an M1 Mac is inconsistent too. Generally it works fine but not always. It uses qemu and doesn't always surface qemu errors when you're building images (you can see the errors when you're running containers, so less of a problem there). They complete build "successfully" and look like valid images when they aren't. I've had multiple k8s deployments fail locally on minikube and on GKE/EKS because of bad images built by Docker on my M1 Mac. The solution is generally rebuild until it works or use my 10 year old Intel-based Mac, but those are bad solves.

Docker shouldn't be charging anyone for that inconsistent experience.

IMO dev.to is what will replace Medium for tech posts. It has a better audience and platform for it than Medium.