This. I found that I was on a different level than my peers in college in terms of programming ability. I knew I was on a different level because we had group work, and it was very annoying having to explain simple things like how to do a linear search for an element in an array. At that point, I believed that some people with CS degrees actually _can\'t_ do fizzbuzz
In the end, I had practiced more and have pretty much programmed everyday for 7 years, while they only did the minimum requirement to pass classes in CS>
What happens here? Does Go suffer from boundary access issues that C has? You know, in Rust, you don't have to worry about that, but is it the same for GO?
Go has null pointers, unlike Rust. Dereferencing a null reference type generally panics, but there are some random exceptions (e.g. indexing a nil map returns a zero value of the appropriate type).
I've run into intermittent issues with net/http (such as the defaults for HttpClient causing application failures in production). It's just a spot you learn to pay attention to. I'm glad they're fixing some of the bugs in the code because otherwise it is an incredible part of the STD lib.
How's Devry? I worked with a person that got a degree from there. It's for-profit too. I can't imagine it's any better than ITT with it's vendor lock in.
In the end, I had practiced more and have pretty much programmed everyday for 7 years, while they only did the minimum requirement to pass classes in CS>