Been primarily using it for two years at Google as IC.

Thanks.

That’s true, but you appear to be a test engineer at Google. Absolutely nothing wrong with that, but it’s also not the same as writing large scale services in Go so I don’t think the experiences are suuuuuper overlapping. I’m a designer and have worked at Google and seen lots of this first hand.

I didn't claim to be writing large scale services? I'm on the team with people who are though.

The code I write is adjacent: refactoring the tests so they run faster with less flakiness (guess what Go makes extremely annoying: mocking concrete types from dependencies! You must either wrap it in your own code (and continuously, manually, maintain that abstraction), give up, or alter the upstream) and writing internal services and tools. Tools are primarily in Go so we can share libraries.

No offense, but a manual tester generally doesnt have much credibility in a conversation about coding matters.

Diminishing a person's job in an attempt to discredit their feedback has even less credibility.

I don't do manual testing. (This is why the majority of people in my role hate the name).