>you need to watch over and destruct goroutines manually to prevent memory leaks No, you don’t. Any stack-allocated resources are freed when the function returns. WaitGroup is just there for synchronization.
Early-career person here. How do you protect yourself from corporate politics?
> I'd be less inclined to unleash a bunch of mid-level devs using Go to create a huge codebase Why?
My propeller hat is a dignified part of my professional attire, thank you very much.
No, they’re right. A non-negligible amount of software engineers in the US make >$1.2M per year.
Your company sounds great. Are you hiring?
Let me know if you need someone to talk with. Contact info is in profile
It's correct. You must be thinking of the Web.
>you need to watch over and destruct goroutines manually to prevent memory leaks No, you don’t. Any stack-allocated resources are freed when the function returns. WaitGroup is just there for synchronization.
Early-career person here. How do you protect yourself from corporate politics?
> I'd be less inclined to unleash a bunch of mid-level devs using Go to create a huge codebase Why?
My propeller hat is a dignified part of my professional attire, thank you very much.
No, they’re right. A non-negligible amount of software engineers in the US make >$1.2M per year.
Your company sounds great. Are you hiring?
Let me know if you need someone to talk with. Contact info is in profile
It's correct. You must be thinking of the Web.