As an up and coming or experienced Go dev, I am sure you are writing tests all over the place! Right? Riiiiiiiiight? Trust, me you better be. There are a million blog posts out there talking about the value of testing your code, so I will sum up why you should test your code in one sentence. Dum dum brain make dum dum mistake, test catch dum dum mistake, you keep job....
Some Things Never Change I have been writing Go for a few years now, but I don’t think that means much. A significant part of my career was working on a Go system for a small ISP where I live. I never really worried about scale; I mostly worried about bugs and race conditions. Now at a large enterprise, I am concerned about distributed systems, ensuring that a service can scale horizontally, and all the fun stuff that comes with a large and busy tech stack....
Hey! Another blog post about something AWS has that is super trendy! It’s basically a must-read! What a unique topic! Ya, I know. What a typical programmer blog I have made by my third blog post. 🤷♂️No point in hiding the fact that I am a vanilla programmer dude, I guess. Maybe this will be the differentiator; DynamoDB was f!&$ing complicated to wrap my head around. So I am writing a blog post for the next person with whatever malfunction I have to accelerate their learning experience....