I'm a high-level infra and devops engineer and team lead.
I've previously run my own team, and previously worked at Mozilla and Facebook. I'm looking for infra/devops lead or senior infra/devops engineer positions.
I'm not looking for pure development positions, but writing scripts, glue, and things like CI - as demanded by infra/devops - are totally fine. I just don't want to be developing the product.
The one thing I can't budge on is that I am exclusively looking for 100% remote positions, due to physical disability. I am based in the UK but I'm happy working with companies anywhere in the world, and capable of shifting my circadian rhythm around to match yours.
My CV is available at cv.dave.io. I am available to start immediately. The CV is a Notion page and can be cloned directly …
I'm looking for work!
I'm a high-level infra and devops engineer and team lead.
I've previously run my own team, and previously worked at Mozilla and Facebook. I'm looking for infra/devops lead or senior infra/devops engineer positions.
I'm not looking for pure development positions, but writing scripts, glue, and things like CI - as demanded by infra/devops - are totally fine. I just don't want to be developing the product.
The one thing I can't budge on is that I am exclusively looking for 100% remote positions, due to physical disability. I am based in the UK but I'm happy working with companies anywhere in the world, and capable of shifting my circadian rhythm around to match yours.
My CV is available at cv.dave.io. I am available to start immediately. The CV is a Notion page and can be cloned directly into your workspace if you use Notion. I'm more than happy to answer any questions, and all leads are graciously appreciated. Drop me a public or private mention, or use the other contact details listed on my CV.
My email address is gated behind a humanity check (don't worry, it's automated) at https://dave.io.
You are very welcome to boost this post, with my thanks.
Containers ensure that software runs reliably no matter where it’s deployed, and Kubernetes is the …
I'm about halfway through this guide to running kubernetes. This book is very well done, with lots of examples that walk the reader through not only effecting changes to their #kubernetes environment, but also really educate the reader as to what's going on under the hood. For all that, it moves along at a quick pace, depending on how much you want to explore or execute variations on some of the commands.
I'm about halfway through this guide to running kubernetes. This book is very well done, with lots of examples that walk the reader through not only effecting changes to their #kubernetes environment, but also really educate the reader as to what's going on under the hood. For all that, it moves along at a quick pace, depending on how much you want to explore or execute variations on some of the commands.
Writing in the previous post in the series about the way I like my interactive shell to be configured, I did touch on the context aspect briefly:Well, OK, maybe the other nicety is using a [...]
I'm a high-level infra and devops engineer and team lead.
I've previously run my own team, and previously worked at Mozilla and Facebook.
I'm looking for infra/devops lead or senior infra/devops engineer positions.
I'm not looking for pure development positions, but writing scripts, glue, and things like CI - as demanded by infra/devops - are totally fine. I just don't want to be developing the product.
The one thing I can't budge on is that I am exclusively looking for 100% remote positions, due to physical disability.
My CV is available at cv.dave.io. I am available to start immediately.
The CV is a Notion page and can be cloned directly into your workspace if you use Notion.
I'm more than happy to answer any questions, and all leads are graciously appreciated. Drop me a …
I'm looking for work!
I'm a high-level infra and devops engineer and team lead.
I've previously run my own team, and previously worked at Mozilla and Facebook.
I'm looking for infra/devops lead or senior infra/devops engineer positions.
I'm not looking for pure development positions, but writing scripts, glue, and things like CI - as demanded by infra/devops - are totally fine. I just don't want to be developing the product.
The one thing I can't budge on is that I am exclusively looking for 100% remote positions, due to physical disability.
My CV is available at cv.dave.io. I am available to start immediately.
The CV is a Notion page and can be cloned directly into your workspace if you use Notion.
I'm more than happy to answer any questions, and all leads are graciously appreciated. Drop me a public or private mention, or use the other contact details listed on my CV.
That's about it. You are very welcome to boost this post, with my thanks.
Sadly, most AI/LLM scraper bots completely ignore website ToS and/or robots.txt.
For those struggling to block those bots on their k8s clusters (using ingress-nginx), here's a handy oneliner I just built. It takes Ichido's blocklist (https://github.com/anthmn/ai-bot-blocker) and transforms it correctly to be used by the ingress controller.
Sadly, most AI/LLM scraper bots completely ignore website ToS and/or robots.txt.
For those struggling to block those bots on their k8s clusters (using ingress-nginx), here's a handy oneliner I just built. It takes Ichido's blocklist (https://github.com/anthmn/ai-bot-blocker) and transforms it correctly to be used by the ingress controller.
welp, got fired after only 2 months. they fired the whole team (including someone who already quit but then they convinced to stay???)
so i am back on the market, unfortunately.
i have plenty of experience as a developer and an SRE. i am primarily skilled with kubernetes, linux, javascript, node, react. ideally i'd focus on the SRE side
i am in canada and available for remote work or on-prem if you're in montreal!
welp, got fired after only 2 months. they fired the whole team (including someone who already quit but then they convinced to stay???)
so i am back on the market, unfortunately.
i have plenty of experience as a developer and an SRE. i am primarily skilled with kubernetes, linux, javascript, node, react. ideally i'd focus on the SRE side
i am in canada and available for remote work or on-prem if you're in montreal!
In episode 8 we talked about how to get started with Kubernetes, and this time we cover the next steps: How to set up ingress and east-west networking, options for restricting access, and the best ways to integrate with your favourite cloud provider.
I’m still processing everything, but I noticed some commonalities in the kinds of challenges #contributors are facing during this 2024 lonely burnout epoch (I’m not the only one who feels it right?)And I wonder if more #maintainers are facing them too.
So what are the toughest #community/ communications/ outreach challenges you’re tackling?
- They only provide a Dockerfile because it's so convoluted and patched together that it would be impossible to create a decent guide on how to make this stuff work without revealing just how much it's all held together by duct tape. Still, taking a peek at the Dockerfile will clearly reveal the chaos at play. - Everything runs in separate containers, as it should, and they have automatic restarts, as they should. But then they're so tightly bound together with, you guessed it, duct tape, that when one of them fails, the container just restarts automatically, leaving the user wondering why everything failed, with only a cryptic error message. - The main container is controlled by Supervisor - which is necessary because everything crashes very often, but the end user doesn't notice because Supervisor restarts the services. To outsiders, everything works fine (but occasionally …
Typical modern software stack:
- They only provide a Dockerfile because it's so convoluted and patched together that it would be impossible to create a decent guide on how to make this stuff work without revealing just how much it's all held together by duct tape. Still, taking a peek at the Dockerfile will clearly reveal the chaos at play. - Everything runs in separate containers, as it should, and they have automatic restarts, as they should. But then they're so tightly bound together with, you guessed it, duct tape, that when one of them fails, the container just restarts automatically, leaving the user wondering why everything failed, with only a cryptic error message. - The main container is controlled by Supervisor - which is necessary because everything crashes very often, but the end user doesn't notice because Supervisor restarts the services. To outsiders, everything works fine (but occasionally throws some errors).
In short, the current trend is to sweep the dirt under the rug. A trendy rug, though!
Are you looking for a freelance developer/architect with:
- Over 20 years of experience in various tech roles. - Success in designing scalable services, both of the monolithic. and microservice variety. - Well versed in designing verification systems based on cryptography. - Expert in writing #Go, and #Python. - Experienced in writing many other languages and frameworks. - Expert in #Linux and #Kubernetes based deployments.
Are you looking for a freelance developer/architect with:
- Over 20 years of experience in various tech roles. - Success in designing scalable services, both of the monolithic. and microservice variety. - Well versed in designing verification systems based on cryptography. - Expert in writing #Go, and #Python. - Experienced in writing many other languages and frameworks. - Expert in #Linux and #Kubernetes based deployments.