MediaLab Online | Site Reliability Engineer / DevOps Engineer | Hybrid & On-Site 2 days/week (Amsterdam, The Netherlands) | https://www.medialab.co
MediaLab is a B2B SaaS platform for distribution, viewing and storage of media assets.
We are seeking a Site Reliability Engineer / DevOps colleague to join our team. As Site Reliability Engineer you will be maintaining and further developing the on-premise/cloud infrastructure for the B2B MediaLab SaaS platform. You will work on varied projects for leading (international) companies within the TV and media industry. Additionally, you will assist with the deployment and integration of our software suite (DevOps).
We are a small but professional team based in Amsterdam providing an enterprise-grade hosted software solution to our international customers. Since we are a small team, this job calls for a flexible mindset but provides a great amount of ownership and responsibility.
Our current hosting stack consists of AlmaLinux 9 running across AWS / Azure / On-Premise automated with Puppet. We are open to people that are willing to learn and not yet meet all requirements.
It's quite fascinating to follow your link and see the amount of "work" required to fix a simple typo. The fix consists of 1 commit with a change of 1 character. It then takes 1 merge request, 1 pipeline, 13 jobs and a grand total of 23 minutes and 41 seconds to process this change and deploy it.
Since one of the big pros of serverless computing is only paying for the resources that you use, I am wondering if we will hit a point where preparing a trivial release is not worth the effort because it's simply too expensive. Paying 23 minutes of cloud computing for a simple typo adds up easily.
Couldn't agree more. If you look at what's happening in the network tab of the developer tools, you'll see it's doing a lot more than providing just a static blog page.
Instead, every x seconds it executes another POST request with pretty much all the details they can gather (scroll from top, scrollable height, referrer etc.).
As soon as you start moving your cursor, the new requests start adding up very quickly, with lots of new params such as "experimentName: readers.experimentShareWidget" or "key: post.streamScrolled".
It really is collecting every single interaction with this page. As it's provided by Medium I'm sure it's part of their data collection program.
Definitely, but after reading some of the responses (e.g. "I ran this script but now my spotlight is missing"), I think too many people skip the learning part.
MediaLab is a B2B SaaS platform for distribution, viewing and storage of media assets. We are seeking a Site Reliability Engineer / DevOps colleague to join our team. As Site Reliability Engineer you will be maintaining and further developing the on-premise/cloud infrastructure for the B2B MediaLab SaaS platform. You will work on varied projects for leading (international) companies within the TV and media industry. Additionally, you will assist with the deployment and integration of our software suite (DevOps). We are a small but professional team based in Amsterdam providing an enterprise-grade hosted software solution to our international customers. Since we are a small team, this job calls for a flexible mindset but provides a great amount of ownership and responsibility.
Our current hosting stack consists of AlmaLinux 9 running across AWS / Azure / On-Premise automated with Puppet. We are open to people that are willing to learn and not yet meet all requirements.
We only accept applicants that are able to work in the EU and have the ability to come to our office 2 days a week. Find more info here: https://www.medialab.co/jobs/site-reliability-engineer-devop... or contact me at pepijn (at) medialab.co.