Our great sponsors
-
Some random Go tips I picked up over time: - Accept interfaces, return concrete types. - Channels are cool, but in many cases you won’t need them. - Check out the defacto standard project layout. I’m using only the “cmd”, “internal”, and “pkg” directories, and already learned a lot from it. - Being able to create type aliases is amazing. In my project I model jobs & tasks, and both have a status. That status is a string, but thanks to type JobStatus string you still can’t accidentally assign a job status to a task or vice versa. - OpenAPI is really nice to generate API code. For learning Go I would definitely recommend hand-writing everything, but once you get the hang of it, check it out.
-
developer-roadmap
Interactive roadmaps, guides and other educational content to help developers grow in their careers.
You can also check https://roadmap.sh/, there are roadmaps for Backend Dev and Go, just don't get overwhelmed by it. As a junior you don't really to know everything that is on the Backend Roadmap to get a job, heck, when I started I had not heard of more than half of that stuff.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Related posts
- What's your go to literature to build Go libraries?
- I'm coming from Java and I have been told that I'm writing go like I'm writing Java. Basically creating structs, injecting fields, and attaching methods. What else can I do?
- Can I point a module to a subdirectory?
- How To Build A Containerized Microservice in Golang: A Step-by-step Guide with Example Use-Case
- Official guide for organizing Go projects and modules