tl;dr:
What is a good start in go?

My wife wants to upgrade her coding skills from „I heard it at college“ to „I actually did something with it“.
I want to learn Go and start coding a bit more. My background is mostly C++ (Backend) and a bit Java (Fronted) some years ago before I went more into testing. For test automation I always use the language that makes the project happy, often Java.

We want want to join forces now, take a vacation and implement a small microservice in Go for my wife’s product (she is a PO) using pair programming.

I want to prepare that a bit. What is a good course or web tutorial to start, that some of you took and can recommend?

Thank you very much!!

Looking into the future to see which features user actually use and which decisions really bite us in the ass.
Alternatively: Force Choke (for reasons). 🤗

!rant, question
Hi, as a developer turned tester I was wondering if anyone here would hear a talk about what on earth testers actually do in a project and how they contribute to the product? I mean besides writing automation scripts or checking if all the requirements are met (the latter is really the most boring part of testing).
I am thinking of doing a talk on this but don't know if Devs might be interested and which conferences I should target.

This will never change...

When small things get big and don't work and you wonder for hours what is wrong with your code ... only to find out the problem is in the framework you use.

I have to start my best moment last year with a confession: I moved from Dev to Test half a decade ago. Naturally I do a lot of automation. My Best moment was when Dev said my automation code is so well structured that he wants to work on that and not an the production code anymore. Gave me that warm "still got it" feeling 😊

When I first started in IT 10 years ago I thought my coworker was pretty weird: every day she brought a coffee mug to the coffee machine and filled it by punching the "espresso" button 7 times. Little did I know this was just a sneak peak into my future...

Lightsabers (I know it's a hardware project).

Advice: always be thankful when you are the idiot because it is easier to change being stupid yourself than changing the other parties stupidity. Example: you can fix wrongly using a 3rd party SDK, but you can most likely not fix internal bugs in the SDK.