The article mentions that by ditching the efficiency cores and lowering the voltage on their new "performance" cores they have achieved the same efficiency. My bachelor is on electronics eng, and my professional career has nothing to do with it. I know there's more to it that that said in the article: Why they've never tried to lower voltage before instead of having efficiency cores? And what do they mean, they lowered voltage, are we talking 5V range to 3V range?
Tell that to millions of lines of stored procedure code across the globe doing heavy lifting on database side. To be clear, I really do not like stored procedures, but they do have their place.
Sorry, I guess, the title doesn't highlight what I am looking for. I am looking for the easiest way to set up a kubernetes cluster on premise. Is there a solution for it? Without using kubeadm and messing with the network.
Some folks mentioned not messing around with kube on-prem. I agree with that, as long as there is another solution that would allow me to easily deploy apps without touching ubuntu and the apps could be resilient and scalable in future with a click of a button. Are there such non-kube solutions?
One way of doing things without kube I imagine as follows: I do coding, build an image and push the container to a container repo. Then I have to ssh into the server and stop and start the container with the new version.
Which I find time consuming. How could I automate this deployment cycle? What people usually do?
You don't need K8s for that, only gitea (with actions enabled) and a server running docker. Actions (like Github Actions) will take care of building, deploying and restarting the container.
The easiest way would be running K3S scripts. You'll have a master and multiple nodes running in minutes. Managing it however... it's a whole different thing.
Thank you, indeed!
I am trying to avoid self management. Considering the complexity of a manual setup, I am looking for some abstraction; "managed" k8s solutions like mentioned above. I have two choices at the moment either go with more or less managed k8s or go with something similar to Heroku (but OSS) with build pipelines.
I'm sure there are solutions that I might be missing...
Noted, thanks! Should I prepare my technical skills more or management/behavioural? I know it varies shop to shop, but still...
The position's title says ".NET Lead with AWS experience".
What strategy to follow when collaborating with devs, keep distance and hierarchy or sam as in a startup would work fine (casual and open)
Just be candid in your conversations with them. Tell them that you're relatively low-yeared in industry but offset that by emphasizing the mentoring you've done your current/previous jobs. I've had employers change the job description based on who they meet in interviews in order to justify bringing me in.
Collaboration: you should know what your coworkers are doing (more or less). Easy "I can prove I did this" mentoring can be something like a Lunch & Learn (teaching about advanced topics in C# or perhaps language features that would benefit the company if they would adopt it). The trendy term "thought leader" is what a mentor does but in a one-to-many instead of one-on-one.
reply