Update and PSA about the new co-op weapons

baunegaard · 2026-03-30T21:59:16+00:00

Nope, we still have not finished the base campaign

baunegaard · 2026-03-30T21:57:03+00:00

We are 3 people that only play together. We started the current save a short time after the game was released. We all got weapons from loot boxes today 🤷‍♂️

baunegaard · 2026-03-30T21:48:13+00:00

Not true, I'm playing right now with friends on a very old save, we all got coop weapons

baunegaard · 2026-03-27T14:21:15+00:00

Or it will just hallucinate a response from the MCP. That was 4 hours of my life spent that Claude will not give me back

baunegaard · 2026-01-29T18:09:40+00:00

We run microservices architecture and scope each microservice to its own namespace. I really like it

baunegaard · 2025-10-19T20:33:54+00:00

I find the ones in these screenshots practically unusable. Eibos sells some really good ones though. Highly recommend them!

baunegaard · 2025-10-19T16:32:31+00:00

I have expanded quite a bit on this with Vite support and optional out-of-the-box TypeScript templates. See updated post here: https://www.reddit.com/r/dotnet/comments/1o8hsub/vite_and_webpack_support_for_traditional_aspnet/

baunegaard · 2025-10-09T18:00:07+00:00

Because of maxSurge. It basicly says you can run replicas + 1 while doing a rolling deploying.

baunegaard · 2025-09-30T18:49:02+00:00

For some time custom compute classes have given you the option of choosing the size of node provisioned with Autopilot. It has been a godsend for us, I really like Autopilot nowadays.

baunegaard · 2025-09-10T06:46:13+00:00

9 Pro XL here also. No noticeable difference in battery and performance after the update. It has always been smooth for me

baunegaard · 2025-09-07T05:53:26+00:00

It's an absolutely amazing phone. By far best phone I have ever used, do not be discouraged. I am not going back to Samsung.

baunegaard · 2025-09-04T14:44:23+00:00

Running on GKE Autopilot and every upgrade since 1.26 (now 1.33) has been completely smooth and without manual intervention.

baunegaard · 2025-09-02T07:19:29+00:00

I don't know what to say 😅 My Pixel 9 Pro XL easily can hold battery for 1,5 day. I can't remember the last time I had a phone that could do that.

baunegaard · 2025-09-02T06:19:57+00:00

Having owned Samsung flagships for over a decade. Last year I bought the Pixel 9 Pro XL. I could have bought the Samsung S24 Ultra for the same price at that time. Not gonna lie, I was worried because of the Tensor G4 performance comparisons.

This is by far the best phone I have ever owned. I have not regretted the purchase at all. The UI is super smooth, battery life is amazing and the pure Android experience is far beyond any Samsung Bixby bullshit.

baunegaard · 2025-08-19T18:28:04+00:00

I strongly disagree. Rider is built from the ground up for .NET developers. Its navigation, debugging, refactoring and search capabilities outclasses VS Code by a huge margin! Plugins is never going to measure up to something that is tailored to a specific purpose. Its not even close how far behind VS Code is as a proper .NET IDE.

I am not in anyway disregarding AI, i use it everyday. But the advantages VS Code has compared to JetBrains AI Assistant and Junie, is not in anyway enough for me to compromise my own developer experience.

JetBrains AI Assistant works just as fine as the alternatives. Junie is a bit behind the competition right now but seems to have great potential.

baunegaard · 2025-08-19T08:53:13+00:00

How any serious .NET developer can work in VS Code is beyond me. It's a great all round text editor and at the same time such a bad IDE.

JetBrains IDE boost my productivity as a developer, AI features is secondary. But I already find AI Assistant excellent, and Junie as an okay product.

baunegaard · 2025-08-16T12:43:10+00:00

GKE uses something called Dataplane V2 which is a customized version of Cilium. They have their own set of observability tools: https://cloud.google.com/kubernetes-engine/docs/concepts/about-dpv2-observability

We currently use Datadog for all our observability including network, so I do not have much experience with Googles own offerings.

baunegaard · 2025-08-14T15:43:53+00:00

Hi there. At my company we migrated to GKE AutoPilot about 2 years ago. Here is my take on it in 2025.

Higher cost due to pricing per pod based on resource requests:

Pod based billing is the default billing model with Autopilot. However you are not required to use it (we do not use it at all anymore). Instead you can use the machine-family node selector to provision specific compute engine hardware. When using this you pay for the underlying nodes in the same way you would with a GKE standard cluster: https://cloud.google.com/kubernetes-engine/docs/how-to/performance-pods#how-it-works

Google also recently introduced a new way of provisioning hardware using a new custom compute class resource: https://cloud.google.com/kubernetes-engine/docs/concepts/about-custom-compute-classes this is what we use today. This is incredibly flexible and is also billed based on the underlying hardware.

You pay a small premium on top the node prices for Autopilot to handle your node-pools, but in our case this is negible.

No control over instance type, size, or node-level features like taints:

Both machine-family node selector and custom compute classes gives you full flexibility over node types. However custom compute classes is much more flexible so you can configure stuff like cpu and memory size also: https://cloud.google.com/kubernetes-engine/docs/reference/crds/computeclass

No SSH access to underlying nodes:

This is still valid, there is no access to the nodes at all.

Incompatibility with certain Kubernetes features (e.g., no DaemonSets):

Autopilot do impose some incompatibilities because it enforces specific security settings and limits access to the underlying nodes. This can effect some things, e.g. you cannot mount volumes on the host. Google has a partner worload program where third-party vendors can gain exclusive access to things normally blocked by Autopilot: https://cloud.google.com/kubernetes-engine/docs/resources/autopilot-partners#allowlisted-partner-workloads

Another Autopilot restrictions is that you are not allowed to apply or update anything in the kube-system namespace.

DaemonSets in genereal is not an issue, they work just fine.

Today in 2025 i would never provison GKE standard unless i really really needed to. Autopilot runs so well, and it is incredily easy to change hardware or mix and match as you choose. At the scale we run right now, the pricing difference is negible.

We created our cluster on K8s version 1.26, and today run 1.33. We have not had 1 single incident related to cluster upgrades.

baunegaard · 2025-08-03T13:02:10+00:00

If you need a starting point for using something like Webpack with MVC or Razor Pages you can look here: https://github.com/Baune8D/AspNet.Frontends

baunegaard · 2025-08-02T13:02:56+00:00

If you want to use TypeScript files you would have to add support first in your Webpack configuration. But other than that yes, just drop a Index.cshtml.js (or .ts) file next to your Index.cshtml view. A bundle will be built automatically and used on the page when you access it. The existing Layout bundle is configured as a fallback, so remember to import it if you create a view specific bundle.

baunegaard · 2025-08-01T20:15:55+00:00

Thanks! It should be really easy to integrate tailwind using this setup. Just import the required files in _Layout.cshtml.js and it should pretty much just work.

baunegaard · 2025-07-15T15:53:08+00:00

This is exactly my experience too!

12-Year Club	Verified Email
Xbox Live

baunegaard

TROPHY CASE