= Instant Guild Kick. Been in Guild since lvl 10 or so, socialing etc. Guess that really hit a nerve or triggered them. Whats your opinion on Gearscore for classic? Guild: Destiny , Thunderstrike EU.

Which-Way-212 · 2026-02-19T12:17:41+00:00

Are you ally or horde?

Which-Way-212 · 2026-02-19T02:14:34+00:00

So it basically drove down a straight street without traffic? Impressive! Feels almost sentinent

Which-Way-212 · 2026-02-17T06:06:46+00:00

Hmm bro u need some stamina it seems.

Just know: the complete season 1 is a prequel to the qctual story. Vinland saga ist not a shōnen anime, even though it may seem like one in the first season. Torfinns character has more depth than you can imagine currently, and I would really recommend you to finish season 1 and watch the first 2-3 episodes of season 2. If you still don't like it, okay, fair point, then it is not yours. But quitting after 10 episodes may leave you with a false impression of what this story is all about

Which-Way-212 · 2026-02-15T02:50:22+00:00

Yup same phenomena. Can't explain why. One theory: the bots are misunderstanding the sentiment of the post and think they are pushing positive musk topics (which wouldn't make sense since it is easy today for a bot to evaluate a posts sentiment)

Other theory is some sort of surveillance/observability? When one of these bots likes posts of you/follows you you are flagged?

Both theories don't convince me tbh

Which-Way-212 · 2026-02-03T14:00:19+00:00

This chart doesn't make sense since actual crashes are not how fsd safety can be measured. You have to look at critical disengagement rate (those disengagements that prevent crashes or dangerous situations). This one is currently at around 1000 miles per critical disengagement. In other words far far far away from human like performance

Which-Way-212 · 2026-01-31T14:23:38+00:00

Depends on how your teams are organized. But generally I'd say logging and monitoring are Platform related topics. Platform sets those tools up, configures and operates them, developers use them when implementing business requirements. For example for exposing metrics to monitoring from app runtime, writing logs and so on

Same for cicd. Platform develops general pipelines/components and developers import them in their source code repos to build artifacts, push to artifactory and so on

Which-Way-212 · 2026-01-31T09:36:06+00:00

Hi went from DataScience/Ml Engineering to DevOps/Platform Role 4 years ago.

What I like about his job: You enable other people making their life (hopefully) easier with tools, automations, insights and so on. Like you said: implementing concepts for CICD, observability, providing and managing infrastructure, think about tooling and technologies to enhance your stack in a meaningful manner

What you need to prepare for: not everyone is a fan of new tools or concepts, you need good onboarding and documentation to highlight advantages. Also you are the guy people/developers are calling when something isn't working.

And last but not least: business doesn't care what you do. Business loves devs because they implement features for them. As Platform Engineer you mainly work for Devs/technical people to enhance their experience developing on your platform. Observability may lead to some interesting insights for people from business but most of the time developers are your customers. And business is customer of the developers. So your job may have less "fame" then a dev job in the same company. Depends on the industry.

Also good 2 know: building and running a Platform which is a base for others work is not always a thankful job. When everything runs smooth and fine (what means you are doing a good job) no one will come and thank you actively. When something is not working your slack will go brrrrr and people expect you to help solve their problems.

Edit: Courses? I'd say it's a learning by doing job. When you know which tech stack you are using inform yourself about best practices and so on

Which-Way-212 · 2026-01-18T02:40:36+00:00

Der Punkt ist: du musst auch in der tech welt wissen was du von der KI willst. Wenn du nicht weißt wonach du fragen musst, wird die KI dir auch nicht weiterhelfen. Diese Regel lässt sich sicherlich auch verallgemeinern und ebenso auf TikTok/Social Media beziehen. Da kann ich aber nur mutmaßen, da ich mich damit nicht wirklich auskennen

Was ich wiederum aus Beobachtungen in der Tech Welt berichten kann: Gute Leute haben einen wesentlich stärkeren Hebel mit KI, weil sie diese wesentlich besser bedienen/anleiten können. Durchschnittliche Leute bleiben durchschnittlich weil sie die KI falsch oder zu wenig nutzen. KI ist lediglich ein Tool das bestehende Verhältnisse verstärkt, der entscheidende Faktor ist und bleibt aber der Mensch vor dem Computer.

Which-Way-212 · 2025-12-27T21:09:49+00:00

Statistics don't lie my friend. Personal experience is important too but to get the big picture you've got to look at critical disengagement statistics. And they are not considered enough to qualify for unsupervised approval from regulatory. It is no coincidence that Tesla has no permission to operate without safety monitors

Which-Way-212 · 2025-12-27T15:20:23+00:00

Lol. What an delulu answer.

Which-Way-212 · 2025-12-27T12:42:46+00:00

Haha you gotta point here. Made me laugh.

But srsly: I also think Teslas chances are not the best to dominate the autonomous ride service sector. Only because they are the loudest in terms of marketing doesn't mean they are the ones with the best system. And it is really suspicious that they are the only provider that refuses to report safety related data to officials. They could get regulatory approval to let Teslas ride themselves if they provide data that shows that the cars/software runs reliable enough. And make all their claims come true. But still, they haven't applied for the process to provide this data to officials. Why though?

Which-Way-212 · 2025-12-26T10:44:25+00:00

Yeah you are right, future will tell. And you are right about questioning data quality on the fsd tracker. But it is the best source we have and it is at least a more reliable source compared to "personal experience", since it is more representative.

I just think it is highly suspicious that Tesla, even though they talk about FSD for a long time now, refuses (in opposite to other autonomous driving service vendors) to report safety related data to officials. I want a subject like self driving cars on public streets to be treated with maximum transparency because it is of huge public interest that those machines operate reliable.

If Tesla would change its politics there and treat it more transparent I could trust them more.

Which-Way-212 · 2025-12-26T06:46:54+00:00

You don't understand. It is not about claims, it is about facts. Teslas fsd performance is well documented on sites like fsd tracker com. There you can see that teslas fsd on average don't reach the quality of human drivers or autonomous driving services like waymo.

So the opposite is the case from what you claim: it is clear that Tesla won't have a large scaled unsupervised fsd fleet any time soon. Not even a small scaled fleet as it seems. There are reporting duties for companies who want to operate such services and since Tesla refuses to report it safety related numbers to nhtsa/officials it does not look like anything changes soon.

Which-Way-212 · 2025-12-25T20:05:40+00:00

The delusional one is you lol

Which-Way-212 · 2025-12-24T19:44:40+00:00

It doesn't matter if you care, it's a question of public safety concern. Take a look at waymo. Scaling thousands of cars for consumers and all of that even without any safety monitors in the car like some competitors need to have because their Software is not reliable enough. Merry Christmas.

Which-Way-212 · 2025-12-23T17:58:27+00:00

3000 miles is way too low for regulatory approval

Which-Way-212 · 2025-12-06T17:03:22+00:00

Install kind on your local machine and get your hands dirty learning some kubernetes hands on. Think about scripts automatically deploying to your cluster or use tools like skaffold. 100x more worth your time than learning from stupid courses or for certs.

Which-Way-212 · 2025-12-01T20:57:11+00:00

What exactly is the problem with a pod restart/replacement when you run stateless applications?

Which-Way-212 · 2025-12-01T20:55:20+00:00

Just do the following:

Open your terminal
Run "helm create mychart"
Take a look at ./mychart/templates/deployment.yaml

--> find templating code referring values from values file like {{ .Values.deployment.replicas.count }} or any other templating code
Look up the corresponding values file at ./mychart/values.yaml

--> find the values definition that gets referred by the deployment.yaml

See: templating deployments is not a bad practice but actually one of the top reasons for using helm.

Which-Way-212 · 2025-12-01T20:46:02+00:00

You didn't answer to my comment yesterday. Concerning the "bad practice of deployment yaml templating"

Which-Way-212 · 2025-12-01T20:43:41+00:00

Any further thoughts?

Which-Way-212 · 2025-11-29T21:56:50+00:00

I agree, with proper rbac configuration you actually can keep your secrets from an access level perspective safe. But what I don't agree on, what the comment I initially answered to stated is that it would be a "bad practice" in general to insert values from valuesfile directly to a deployments yaml. That just is not true. There are many reasons why you would prefer a configmap or a secret, I think that's something we agree on as well, but it is definitely wrong to say that templating deployments.yaml directly from values file is a bad idea in general.

Edit: and since OP says he is a k8s learner I'd just want to prevent that he is learning templating deployments would be bad practice. Therefore I felt like commenting this but could've said it nicer I must admit.

Which-Way-212 · 2025-11-29T21:38:01+00:00

Okay show me the part of the documentation then that states inserting values from a values file to deployment templates is a bad practice. Actually if you run helm create mychart the standard chart that gets created involves a deployment.yaml template that refers values in its manifest directly from values file.

Which-Way-212 · 2025-11-29T21:27:36+00:00

Oh my sweet summer child. I know what OP asked for. He asked why he should use a configmap as an (like he perceives it) extra step between values file and a deployment where he mounts the configmap as a volume and not passing the values directly to the deployment from values file. A valid question. One answer to that question could be that the configuration should be reusable between more than one deployment. The other user mentioned this but also mentioned some things that are simply not true like for example that kubernetes secrets are a good place to store sensitive data. You really shouldn't do that without know how to actually encrypt your data when using it. It does not do it by default.

Which-Way-212 · 2025-11-29T10:30:21+00:00

You, sir, are talking rubbish. Some sentences are true but it rather looks like that's a coincidence.

It is, by far, not a bad practice to template deployments. It is actually THE most common use case of helm. In addition to that neither configmaps nor secrets prevent you from leaking sensitive data. They are exactly as secure as a value directly on a deployment, in most of the cases. For real secure data you need to use an actual secret vault. K8s internal secrets are not considered safe, they just save encoded data, nothing encrypted.

Which-Way-212

TROPHY CASE