glad you got the teapot

its critical because without proper tonal enunciation the words can be ambiguous.

it heard wu2 but i heard wo2 from you fine. and it should sound like wo2 not wo3 if spoken quickly. not a native speaker though so i could be wrong

How much of their imported goods are produced in countries with dirty energy?

If you want to go in that direction, you might rather want to argue that norway sold and sells directly lots of oil themself for other countries.

But for me, that does not change the fact, that they still did great making the investment in EV.

You have to start somewhere.

is this whataboutism?

Yea well the other thing is zabka is an awesome store, the amazon store sucked

i didnt use their system, but the experience wasnt that great, it felt like a target grocery store in terms of product quality and selection. its a grocery store, but the regular grocery store is better.

I agree, as a pretty experienced coder, I wonder if the newer generation is just rolling with the first shot. I find myself having the AI rewrite things a slightly different way 2-3x per feature or maybe even 10x. Because i know quality when i see it, having done so much by hand and so much reading.

But there is bad code and good code and SREs cant tell you which is which, nor fix it.

Why not? I'm a SWE SRE and I'm arguably better at telling good code from bad code than many of the pure devs I've worked with.

Edit: ^ At the cost of being much worse at being able to tell what features are useful or well implemented.

My take (I'm an SRE) is that SRE should work pre-emptively to provide reproducible prod-like environments so that QA can test DEV code closer to real-life conditions. Most prod platforms I've seen are nowhere near that level of automation, which makes it really hard to detect or even reproduce production issues.

And no, as an SRE I won't read DEV code, but I can help my team test it.

>And no, as an SRE I won't read DEV code, but I can help my team test it.

that doesn't sound like my definition of an SRE. How is what you're doing different than Ops?

> And no, as an SRE I won't read DEV code, but I can help my team test it.

I mean to each their own. Sometimes if I catch a page and the rabbit hole leads to the devs code, I look under the covers.

And sometimes it's a bug I can identify and fix pretty quickly. Sometimes faster than the dev team because I just saw another dev team make the same mistake a month prior.

You gotta know when to cut your losses and stop searching the rabbit hole though, that's true.

I agree with your nuance, but that's not my default mode, unless I know the language and the domain well I am not going to write an MR. I'm going to read the stack trace to see it it's a conf issue though.

I review it as i generate it. for quality. i guide it to be self-testing. create unit tests and integration tests according to my standards

yeah its like im being hypnotized and im forced to wait until programming is over