We can go further, I think it’s impossible to prevent memory leaks in a general purpose language
We can go further, I think it’s impossible to prevent memory leaks in a general purpose language
WTF I didn’t understand, thanks for the explanation. The fact that it’s used all around the world in big companies doesn’t matter I guess.
I was so lucky in the interview for my current job: I’m working on a product with a big networking component, and I was asked to write an echo server with low level components. That was maybe the second time I had a test related to the job.
Why the fuck would they prevent private browsing? I use that a lot to be sure the session is closed correctly.
My coworkers do document the code:
/// Returns a list of foos, given a bar.
fn get_foos_from_bar(bar: Bar)
I have a degree in philosophy (and no other diploma) and I make $200k/year as a senior developer. The degree does not really matter.
I think they just don’t like cringe
As said my sibling comment, I use KDE connect with GNOME shell
It depends if it’s a real DevOps role, or an operations role with a DevOps title because it’s trendy. In the former case, the role should include some kind of backend development.
When senior devs get older, they’re tired to look cool and take care of their eyes with light themes.
And here you’re only talking about a subset of memory leaks, by inaccessible memory. You can also leak memory by pushing new elements in a channel while never reading them for example.