Ford Pro Tech | Software engineering (multiple roles) | Full-time | REMOTE | https://fordpro.com
Ford Pro is a new global business within Ford committed to commercial customer productivity. Ford Pro delivers a work-ready suite of vehicles, accessories and services for virtually every vocation, backed by technology and engineered for uptime. A true one-stop shop, offering a full portfolio of electrified and internal combustion vehicles designed to integrate seamlessly with the Ford Pro ecosystem, helping customers' businesses thrive today and into the new era of electrification.
Sorry, I suppose being a professional musician is one field with similar requirements for skill versus pay. Nobody's going to pay any money to a middle-quintile piano player, just like nobody in academia is going to pay any money to a freshly-minted middle-quintile PHD.
I felt this way at some point when I worked at LANL. I specifically remember a training module that said it was not inclusive or respectful to require or insist that coworkers speak a specific language unless it impacted your job function. After all, they dont 'owe' you anything to make you feel comfortable in social settings. And even if they are talking about your project that doesnt mean they need your input..
On the other hand, when I worked at a small German startup our CEO would constantly remind our team to 'speak English for nc!' -- but usually only when he wanted to make sure I was aware, bolster their own skills to continue to expand internationally or when he thought I might be able to contribute. I appreciated that it did also make me feel awkward when I could tell that speaking English made it more challenging for them to convey ideas effectively.
I recommend Pimsleur language classes to get started and meet them in the middle.
It took me a long time to come to terms with this fact. I was once asked during an interview what I wouldnt run in k8s and I said legacy apps and hardware specific apps. Now I think that for many applications cloud run or cloud function can reduce the complexity of software delivery. It takes a team just to manage the k8s infra while an app team can be responsible for their own cloud run app.
When I talk to people about k8s, if they haven't containerized their apps yet, I generally recommend starting with a simple CAAS setup and then, if you need some of the flexibility and power that k8s provides, then move those apps into a cluster.
It can do a lot of cool stuff, but there's plenty of complexity there, and there are quite a few potential nasty surprises in there (from a security standpoint anyway, which is where I focus)
OP is using google cloud/GCP, cloud functions and cloud run are google cloud serverless offerings. Cloud functions is comparable to lambda, cloud run is basically a kubernetes-based PaaS.
CFs are higher level than Lambda, they can implement HTTP endpoints directly. More like Serverless framework, or a combination of API Gateway + Lambda. And they have good container support, Lambda container support is a bit iffy.
Thanks both for explaining. Now I understand why, recently AWS Lambda added support for invocation URLs. Or I thought they did but the page seems to have been taken down now.
