11 karma · joined October 21, 2014
With respect to your second point, I see what you mean but I still don't think that's a negative of Go. You can pass in copied values without having to have a deep_copy() primitive (loop map values and copy to new map, dereferencing a pointer, etc.). Like other parts of Go, if you want to make your data immutable there is no syntactic sugar. You have to explicitly write it out.
Here's a playground for reference:
I’m the developer behind BuildEngine (https://buildengine.dev/), a tool that build games on a remote server.
BuildEngine lets you run builds faster, run multiple builds in parallel, and maintain consistent architecture across builds. BuildEngine is also compatible with all major game engines and can be easily integrated into your existing CI / CD pipeline (e.g. GitLab, TeamCity, etc.)
We want to give indie game devs and their teams the same tools as larger AAA studios without the overhead of managing their own servers. Game development is hard enough as it is already and so we want to do our part to make it a little easier :)
Would love to hear your honest feedback! Let me know if you have any questions.
Thanks all!
I also came into tech from a non-traditional background and I struggled at the beginning to get my foot in the door. I studied math and econ in school, and even though my passion was writing software, it was hard to start applying without any projects or connections in the field.
To find a job, I spent money on a coding bootcamp post-graduation from college. This seemed like the only option at the time. If there was something like this at the time, I would have rather have gone that route instead.
Full disclosure, this is a new platform that I've been building for the last few months. Even though it's something I've worked on, I do think it's an important conversation to have and thought this would be the best place to host it. If you have any feedback, I would appreciate that as well.