in Transformers 3, there is a good example about this.
Sam wanted a job that matters, so he rejects the offer. Then the conversation follows along the lines of: "you want the job after this job, but this is the job standing in the way".
In this context, I understand by that: focus on career progression, and then switch to "save the world".
Steganography is about hiding information within other information, but I don't really see what's the point you are trying to make here. Could you elaborate?
Basically every company have their own definition. For some companies, a SRE is just a traditional software engineer who happens to know how to use Kubernetes, where for others, a SRE is a "modern systems guy", with focus on IaC and automation.
Guess you're experiencing the same but regarding ML.
I've reading about this "security professionals shortage" for quite some years, yet the reality is that there is no such shortage.
And I think this is even expandable now to any IT field. People keep saying about shortage, but what I do see is exhausting hiring process most people just don't want to deal with.
Why would you install postgres through Brew though?
Those times are way gone, that's the purpose of containers.
I've been using Brew for a while to just install "core" packages like python, curl, wget and such, and everything else like a postgres, nginx, whatever..a go to a container.
Is this even relevant nowadays? I've been doing some tests with Edge and Firefox, and with their built-in tracking prevention + uBlock, it didn't matter whether I accepted all or only essential cookies, because at the end, only first party cookies are set.
One might argue that accepting all allows tracking by the site itself. But, does it really matter? I'm already on the site because I'm willing to. At this point, we're no longer talking about tracking but analytics.
IMO, age is not a problem but time management and responsibilities as others have mentioned. If you are raising kids or taking care of elder people, but you have poor management skills, or maybe you're just overwhelmed... then it's going to be problem to learn something, even if it's improving your knowledge in something you're already familiar with.
Disclaimer: I have only interviewed for junior positions.
I never focus on algorithms or particular technologies. When I interview someone, I'm looking for two things:
- First and most important: we both are in the same wave. I want to make sure the applicant understands what's the goal of the position. For example, once a guy with over 10+ of experience applied for a junior position but demanding responsibilities and salary of a senior.
- Second, expose a general problem and work with the applicant to get an idea about what can we do. I don't expect a solution in 5 minutes, I'm looking for ideas of how we can tackle this problem and how we would start working on it.
Sam wanted a job that matters, so he rejects the offer. Then the conversation follows along the lines of: "you want the job after this job, but this is the job standing in the way".
In this context, I understand by that: focus on career progression, and then switch to "save the world".