Remote: Only. Open-minded to occasional travel.
Willing to relocate: No
Technologies: Python, Postgres, Flask, Containers, k8s, Ansible, Terraform, Helm, Linux, various clouds. Currently learning Rust. Etc...
Resume/CV: https://www.linkedin.com/in/kurtismullins or https://www.kurtismullins.com (WIP)
Email: hire@kurtismullins.com
18 Years Web, SaaS, Full-Stack, Backend, and SRE/DevOps/Platform Engineering.
Looking for freelance clients/projects and part-time opportunities.
Would love to work with universities, research institutes, public good non-profits, and so forth but open to working with all kinds of wonderful people!
Work-life balance is my goal over getting rich; if you support my lifestyle then I am happy to reciprocate with my time & skills.
At home, you can find me homesteading and exploring merging tech knowledge with the natural, real world. Currently refreshing my old electronics skills to build sensors and automation systems for various projects around the house (e.g. growing food, rain water collection, etc..)
I have recently traveled to Boston a few times (its ~3 hours by train) and its amazing! Would love to make some connections down there as well. I can't come down every day but am open-minded to dropping in every once in a while.
I also really want to check out MIT (swap meet & library!), FSF, and all of this super cool culture in Boston that was too far away when I used to live in Ohio.
Thanks!"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (May 2026)"}},"_tags":["comment","author_pigsinzen","story_47975570"],"author":"pigsinzen","comment_text":"Location: Maine (USA)
Remote: Only. Open-minded to occasional travel.
Willing to relocate: No
Technologies: Python, Postgres, Flask, Containers, k8s, Ansible, Terraform, Helm, Linux, various clouds. Currently learning Rust. Etc...
Resume/CV: https://www.linkedin.com/in/kurtismullins or https://www.kurtismullins.com (WIP)
Email: hire@kurtismullins.com
18 Years Web, SaaS, Full-Stack, Backend, and SRE/DevOps/Platform Engineering.
Looking for freelance clients/projects and part-time opportunities.
Would love to work with universities, research institutes, public good non-profits, and so forth but open to working with all kinds of wonderful people!
Work-life balance is my goal over getting rich; if you support my lifestyle then I am happy to reciprocate with my time & skills.
At home, you can find me homesteading and exploring merging tech knowledge with the natural, real world. Currently refreshing my old electronics skills to build sensors and automation systems for various projects around the house (e.g. growing food, rain water collection, etc..)
I have recently traveled to Boston a few times (its ~3 hours by train) and its amazing! Would love to make some connections down there as well. I can't come down every day but am open-minded to dropping in every once in a while.
I also really want to check out MIT (swap meet & library!), FSF, and all of this super cool culture in Boston that was too far away when I used to live in Ohio.
Thanks!","created_at":"2026-05-02T14:54:40Z","created_at_i":1777733680,"objectID":"47986932","parent_id":47975570,"story_id":47975570,"story_title":"Ask HN: Who wants to be hired? (May 2026)","updated_at":"2026-05-02T14:57:44Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"evaneykelen"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Return | REMOTE | DevOps / Platform engineer | Full-time
Return (https://return.energy) is hiring a DevOps engineer who will build and run the infrastructure behind platforms that accelerate the transition to carbon-free energy. Return's main activity is building and operating industrial-size Battery Energy Storage Systems. Our operations are located in the Netherlands, Germany, Belgium, and Spain. You will be making a measurable (country-level) impact on the transition to renewable energy. Return recently raised \u20ac300M to support its growth.
While we employ over 120 people, Return's technical team is still small (15 people). Our platform automates processes in energy storage, monitoring, market optimization, sales, project management, procurement, construction, and customer service. Behind it sits a mix of EU cloud and on-site compute at our battery sites, with strict uptime and security requirements.
During the first four years of operation, we laid the foundation for our platforms, and we are ready to scale up. This is why we are looking for an experienced DevOps engineer who can own the full picture: cloud environments, self-hosted infrastructure at our BESS sites, and the operations centers in Amsterdam and Eindhoven from which we run the fleet.
Your primary focus will be to design, automate, and operate the infrastructure that our virtual battery platform runs on. That means EU-only cloud providers for application workloads, hardened on-premise setups at our sites, and the connectivity in between. You will be the person who decides what gets deployed where, and who makes sure it stays up and stays secure.
https://jobs.polymer.co/return/39863"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who is hiring? (May 2026)"}},"_tags":["comment","author_evaneykelen","story_47975571"],"author":"evaneykelen","children":[47997362],"comment_text":"Return | REMOTE | DevOps / Platform engineer | Full-time
Return (https://return.energy) is hiring a DevOps engineer who will build and run the infrastructure behind platforms that accelerate the transition to carbon-free energy. Return's main activity is building and operating industrial-size Battery Energy Storage Systems. Our operations are located in the Netherlands, Germany, Belgium, and Spain. You will be making a measurable (country-level) impact on the transition to renewable energy. Return recently raised \u20ac300M to support its growth.
While we employ over 120 people, Return's technical team is still small (15 people). Our platform automates processes in energy storage, monitoring, market optimization, sales, project management, procurement, construction, and customer service. Behind it sits a mix of EU cloud and on-site compute at our battery sites, with strict uptime and security requirements.
During the first four years of operation, we laid the foundation for our platforms, and we are ready to scale up. This is why we are looking for an experienced DevOps engineer who can own the full picture: cloud environments, self-hosted infrastructure at our BESS sites, and the operations centers in Amsterdam and Eindhoven from which we run the fleet.
Your primary focus will be to design, automate, and operate the infrastructure that our virtual battery platform runs on. That means EU-only cloud providers for application workloads, hardened on-premise setups at our sites, and the connectivity in between. You will be the person who decides what gets deployed where, and who makes sure it stays up and stays secure.
https://jobs.polymer.co/return/39863","created_at":"2026-05-01T16:36:08Z","created_at_i":1777653368,"objectID":"47976769","parent_id":47975571,"story_id":47975571,"story_title":"Ask HN: Who is hiring? (May 2026)","updated_at":"2026-05-03T14:37:33Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"wutwutwat"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"It's not just low level, in most cases, it's also overkill.
Most companies aren't "web scale" \u2122 and don't need an orchestrator built for google level elasticity, they need a vm autoscaling group if anything.
Most apps don't need such granular control over fs access, network policies, root access, etc, they need `ufw allow 80 && ufw enable`
Most apps don't need a 15 stage, docker layer caching optimized, archive promotion build pipeline that takes 30 minutes to get a copy change shipped to prod, they need a `git clone me@github.com:me/mine.git release_01 && ln -s release_01 /var/www/me/mine/current`
This is coming from someone who has had roles both as a backend product engineer and as a devops/platform engineer, who has been around long enough to remember "deploy" to prod was eclipse ftping php files straight to the prod server on file save. I manage clusters for a living for companies that went full k8s and never should have gone full k8s. ECS would have worked for 99% of these apps, if they even needed that.
Just like the js ecosystem went bat shit insane until things started to swing back towards sanity and people started to trim the needless bloat, the same is coming or due for the overcomplexity of devops/backend deployments"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"I am building a cloud"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://crawshaw.io/blog/building-a-cloud"}},"_tags":["comment","author_wutwutwat","story_47872324"],"author":"wutwutwat","children":[47875677,47890997],"comment_text":"It's not just low level, in most cases, it's also overkill.
Most companies aren't "web scale" \u2122 and don't need an orchestrator built for google level elasticity, they need a vm autoscaling group if anything.
Most apps don't need such granular control over fs access, network policies, root access, etc, they need `ufw allow 80 && ufw enable`
Most apps don't need a 15 stage, docker layer caching optimized, archive promotion build pipeline that takes 30 minutes to get a copy change shipped to prod, they need a `git clone me@github.com:me/mine.git release_01 && ln -s release_01 /var/www/me/mine/current`
This is coming from someone who has had roles both as a backend product engineer and as a devops/platform engineer, who has been around long enough to remember "deploy" to prod was eclipse ftping php files straight to the prod server on file save. I manage clusters for a living for companies that went full k8s and never should have gone full k8s. ECS would have worked for 99% of these apps, if they even needed that.
Just like the js ecosystem went bat shit insane until things started to swing back towards sanity and people started to trim the needless bloat, the same is coming or due for the overcomplexity of devops/backend deployments","created_at":"2026-04-23T11:15:16Z","created_at_i":1776942916,"objectID":"47874351","parent_id":47874237,"story_id":47872324,"story_title":"I am building a cloud","story_url":"https://crawshaw.io/blog/building-a-cloud","updated_at":"2026-04-24T17:42:33Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"SOLAR_FIELDS"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Indeed. The use case is like this: I'm a Devops/Platform/SRE/Infra/WhateverYouCallAWSAdminInYourOrg at BigCorp and end users are asking me to use software XYZ. It's on the AWS Marketplace. I have two choices. I could either
1. Go through a 1-2 month procurement process where I have to deal with not only the vendor's sales team on who I'm buying from but also probably multiple teams in my BigCorp. Vendor sales team wants to feel relevant and so I'm sitting in at least one meeting where I'm telling them I just want to buy your shit make it as fast as possible. But then the people in my BigCorp likely not only don't understand why the software is necessary, but need to feel relevant and as such will make me fight through bureaucratic hurdles. I have to get compliance involved. Finance involved. If there's a procurement team I have to get them involved. Probably there's a security questionnaire that my bigcorp's security team uses. I have to send that to the vendor's sales people. They have to send it to their security folks. Security folks on their end have to complete it and send it back. I have to send approvals up the chain on my end, after I've successfully convinced some clueless nontechnical user why software XYZ is important and no, the shit half baked thing we already have doesn't work.
OR alternatively:
2. I can go to the AWS marketplace, click a button, and now my AWS bill goes up X thousands of dollars per month and none of the bullshit from 1 is required. Because AWS is already an approved vendor. Everyone except perhaps someone monitoring the AWS bill for large increases is happy and doesn't care (well, maybe the security team does, but hopefully they aren't tattling on you to the procurement people who have nothing to do and want to stick their fingers in the process and we can make that process go quick), and I just need to tell that person that we are doing it.
It's not always the exact narrative I just laid out, but the gist of it is pretty much procurement at every bigcorp."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Changes to GitHub Copilot individual plans"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://github.blog/news-insights/company-news/changes-to-github-copilot-individual-plans/"}},"_tags":["comment","author_SOLAR_FIELDS","story_47838508"],"author":"SOLAR_FIELDS","comment_text":"Indeed. The use case is like this: I'm a Devops/Platform/SRE/Infra/WhateverYouCallAWSAdminInYourOrg at BigCorp and end users are asking me to use software XYZ. It's on the AWS Marketplace. I have two choices. I could either
1. Go through a 1-2 month procurement process where I have to deal with not only the vendor's sales team on who I'm buying from but also probably multiple teams in my BigCorp. Vendor sales team wants to feel relevant and so I'm sitting in at least one meeting where I'm telling them I just want to buy your shit make it as fast as possible. But then the people in my BigCorp likely not only don't understand why the software is necessary, but need to feel relevant and as such will make me fight through bureaucratic hurdles. I have to get compliance involved. Finance involved. If there's a procurement team I have to get them involved. Probably there's a security questionnaire that my bigcorp's security team uses. I have to send that to the vendor's sales people. They have to send it to their security folks. Security folks on their end have to complete it and send it back. I have to send approvals up the chain on my end, after I've successfully convinced some clueless nontechnical user why software XYZ is important and no, the shit half baked thing we already have doesn't work.
OR alternatively:
2. I can go to the AWS marketplace, click a button, and now my AWS bill goes up X thousands of dollars per month and none of the bullshit from 1 is required. Because AWS is already an approved vendor. Everyone except perhaps someone monitoring the AWS bill for large increases is happy and doesn't care (well, maybe the security team does, but hopefully they aren't tattling on you to the procurement people who have nothing to do and want to stick their fingers in the process and we can make that process go quick), and I just need to tell that person that we are doing it.
It's not always the exact narrative I just laid out, but the gist of it is pretty much procurement at every bigcorp.","created_at":"2026-04-22T15:31:44Z","created_at_i":1776871904,"objectID":"47865060","parent_id":47862074,"story_id":47838508,"story_title":"Changes to GitHub Copilot individual plans","story_url":"https://github.blog/news-insights/company-news/changes-to-github-copilot-individual-plans/","updated_at":"2026-04-24T20:01:15Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tenaka"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"I\u2019m a Senior DevOps / Platform Engineer with about 8 years focused on infrastructure, and a 15 year background in PHP before that. I\u2019ve spent time on both the application and infrastructure sides of production systems, which helps when debugging or designing changes. Over the years I\u2019ve moved deeper into cloud infrastructure, CI/CD, and reliability work \u2014 mostly trying to eliminate recurring failure points instead of layering on quick fixes. I care a lot about long-term system health and building platforms that stay stable as they grow.
Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.com Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.com- ETH Watchtower: a real-time EVM monitoring tool with heuristics and classification of contracts and transactions: https://ethwatchtower.xyz
- P2P SSL VPN provider/consumer tools using a blockchain as announcement and settlement layer: https://github.com/rnts08/blockchain-vpn
- OrdexNetwork: https://ordexnetwork.org, I've built https://ordexswap.online and https://ordexswap.online/wallet/ as well as an Umbrel variant of a self-hosted wallet.
- Waya Wolf Coin v3: Helped the team to compile binaries for linux, and modernizing the libraries: https://github.com/rnts08/WWC3-Linux-binaries / https://github.com/Waya-Wolf/WWC3
- Low Cap Exchange algorithmic trading bots with machine learning and automatic ghost trading, because I wanted to see what the most common shapes are on smaller exchanges: https://github.com/rnts08/low-cap-exchange-trading-bot
However, I am really looking for Sr. DevOps/Platform Eng/SRE/System/Network Admin/Infra Engineering or similar, full-time or contract work, see https://timhbergstrom.pro for contact details."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: What Are You Working On? (April 2026)"}},"_tags":["comment","author_rnts08","story_47741527"],"author":"rnts08","comment_text":"Since blacksmith labs and phoenix ai - the ai assisted automotive r&d, security and compliance engineering tool has been on the backburner for a while, I've been helping a couple of blockchain projects and built some tools, besides tinkering with my real-time EVM contract and transaction heuristics and classification engine.
- ETH Watchtower: a real-time EVM monitoring tool with heuristics and classification of contracts and transactions: https://ethwatchtower.xyz
- P2P SSL VPN provider/consumer tools using a blockchain as announcement and settlement layer: https://github.com/rnts08/blockchain-vpn
- OrdexNetwork: https://ordexnetwork.org, I've built https://ordexswap.online and https://ordexswap.online/wallet/ as well as an Umbrel variant of a self-hosted wallet.
- Waya Wolf Coin v3: Helped the team to compile binaries for linux, and modernizing the libraries: https://github.com/rnts08/WWC3-Linux-binaries / https://github.com/Waya-Wolf/WWC3
- Low Cap Exchange algorithmic trading bots with machine learning and automatic ghost trading, because I wanted to see what the most common shapes are on smaller exchanges: https://github.com/rnts08/low-cap-exchange-trading-bot
However, I am really looking for Sr. DevOps/Platform Eng/SRE/System/Network Admin/Infra Engineering or similar, full-time or contract work, see https://timhbergstrom.pro for contact details.","created_at":"2026-04-13T05:16:23Z","created_at_i":1776057383,"objectID":"47747864","parent_id":47741527,"story_id":47741527,"story_title":"Ask HN: What Are You Working On? (April 2026)","updated_at":"2026-04-13T05:39:31Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"Uncle-iroh"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Location: Texas (open to relocation anywhere in US)
Remote: Yes
Willing to relocate: Yes
Technologies: AWS, Kubernetes, Helm, Terraform, Ansible, GitHub Actions, Docker, Linux, Python, Bash, Prometheus, Grafana\nR\u00e9sum\u00e9/CV: https://drive.google.com/file/d/1sjewwU4Vjs9rXhkoHNvNIrJt1ZC...
Email: dm2606700@gmail.com
Brief: DevOps/Platform Engineer focused on automation. Cut deployment times 75% (20min to 5min) by implementing a GitHub Actions CI/CD pipeline for a K3s cluster. I build production ready IaC with Terraform and manage containerized workloads with Helm. Zero hand holding required on the Linux/CLI side."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (April 2026)"}},"_tags":["comment","author_Uncle-iroh","story_47601858"],"author":"Uncle-iroh","comment_text":"Location: Texas (open to relocation anywhere in US)
Remote: Yes
Willing to relocate: Yes
Technologies: AWS, Kubernetes, Helm, Terraform, Ansible, GitHub Actions, Docker, Linux, Python, Bash, Prometheus, Grafana\nR\u00e9sum\u00e9/CV: https://drive.google.com/file/d/1sjewwU4Vjs9rXhkoHNvNIrJt1ZC...
Email: dm2606700@gmail.com
Brief: DevOps/Platform Engineer focused on automation. Cut deployment times 75% (20min to 5min) by implementing a GitHub Actions CI/CD pipeline for a K3s cluster. I build production ready IaC with Terraform and manage containerized workloads with Helm. Zero hand holding required on the Linux/CLI side.","created_at":"2026-04-09T00:28:31Z","created_at_i":1775694511,"objectID":"47697885","parent_id":47601858,"story_id":47601858,"story_title":"Ask HN: Who wants to be hired? (April 2026)","updated_at":"2026-04-14T08:27:50Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"TamasSzigeti"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Backstory: At work I had to build an AI pipeline to run millions of prompts. First I just put the prompts into string consts and integrated directly with api, chaining one run onto the output of another \u2013 but it quickly became a maintenance nightmare. Iterating on prompts, testing them over datasets, experimenting with different chaining did not fit into the regular sdlc and running them at our scale was quite difficult as most of the time is spent on waiting for the api response while holding on to dear server resources.
So we started using PromptLayer in order for the prompt engineer to build evals there, edit-improve prompts outside the code and chaining them together however he likes, and we were also running them on their infra. But the UI was cumbersome and the latency was disappointing and given other issues and having found no better alternative it triggered me into starting to build a better alternative.
One year and countless nights and weekends later I have what I like to call an IDE for AI, or more like a full DevOps platform as it goes from development of prompts and workflows through testing them all the way through the running infra. I tried to squeeze every nanosecond out of the stack, hyper-optimising every part of it to have as little overhead above the AI calls themselves as possible.
Docs: https://docs.promptjuggler.com
App: https://promptjuggler.com
I built this with love and it's my first post here, so please be gentle (:"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: PromptJuggler \u2013 A dev env and runner for prompts, workflows, agents"},"url":{"matchLevel":"none","matchedWords":[],"value":"https://promptjuggler.com"}},"_tags":["story","author_TamasSzigeti","story_47679019","show_hn"],"author":"TamasSzigeti","created_at":"2026-04-07T18:01:29Z","created_at_i":1775584889,"num_comments":0,"objectID":"47679019","points":3,"story_id":47679019,"story_text":"Backstory: At work I had to build an AI pipeline to run millions of prompts. First I just put the prompts into string consts and integrated directly with api, chaining one run onto the output of another \u2013 but it quickly became a maintenance nightmare. Iterating on prompts, testing them over datasets, experimenting with different chaining did not fit into the regular sdlc and running them at our scale was quite difficult as most of the time is spent on waiting for the api response while holding on to dear server resources.
So we started using PromptLayer in order for the prompt engineer to build evals there, edit-improve prompts outside the code and chaining them together however he likes, and we were also running them on their infra. But the UI was cumbersome and the latency was disappointing and given other issues and having found no better alternative it triggered me into starting to build a better alternative.
One year and countless nights and weekends later I have what I like to call an IDE for AI, or more like a full DevOps platform as it goes from development of prompts and workflows through testing them all the way through the running infra. I tried to squeeze every nanosecond out of the stack, hyper-optimising every part of it to have as little overhead above the AI calls themselves as possible.
Docs: https://docs.promptjuggler.com
App: https://promptjuggler.com
I built this with love and it's my first post here, so please be gentle (:","title":"Show HN: PromptJuggler \u2013 A dev env and runner for prompts, workflows, agents","updated_at":"2026-04-08T05:20:11Z","url":"https://promptjuggler.com"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"anon7000"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Yeah, I mean Deno\u2019s success is predicated on enterprises moving production apps from NodeJS to Deno. Node is extremely established and entrenched, and migrating the goddamn runtime of a large production server is not usually an easy project. If I have a 5-10 year old Node project, it might work well on Deno, but almost no one has the time to champion a migration when it just doesn\u2019t have that many benefits.
Yes, it comes with batteries included, but a big node project already has setups handling things like testing, linting, formatting, and dependencies. Moving to Deno for any of those might actually be easy, but migrations in the JS ecosystem never end up being easy, so people who could sway the company to change tools don\u2019t have the appetite to tell leadership about migration projects with minimal upside and unknown duration. And under a startup with an unknown future.
NodeJS succeeded at undermining existing server toolchains, because web devs were easily sold on writing JS for their servers, so tons of successful startups built with Node, and when Node got pretty well established, it was easier to adopt for greenfield projects in the enterprise.
Deno is Node, but better. So it\u2019s not giving a whole market of devs access to a tool that is way easier to write for. It\u2019s marginally easier to manage and you could maybe drop some other toolchain dependencies. But again, those toolchain things are automated/hidden away from developers directly\u2026 like they don\u2019t care we use eslint, they just care CI catches problems before they hit prod and that the linter throws an error early in the process. It\u2019s already easy for them to run locally. So it\u2019s not like Deno lint changes anything about the dev user experience, it just changes what DevOps/platform teams have to manage."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"404 Deno CEO not found"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://dbushell.com/2026/03/20/denos-decline-and-layoffs/"}},"_tags":["comment","author_anon7000","story_47467746"],"author":"anon7000","children":[47476421],"comment_text":"Yeah, I mean Deno\u2019s success is predicated on enterprises moving production apps from NodeJS to Deno. Node is extremely established and entrenched, and migrating the goddamn runtime of a large production server is not usually an easy project. If I have a 5-10 year old Node project, it might work well on Deno, but almost no one has the time to champion a migration when it just doesn\u2019t have that many benefits.
Yes, it comes with batteries included, but a big node project already has setups handling things like testing, linting, formatting, and dependencies. Moving to Deno for any of those might actually be easy, but migrations in the JS ecosystem never end up being easy, so people who could sway the company to change tools don\u2019t have the appetite to tell leadership about migration projects with minimal upside and unknown duration. And under a startup with an unknown future.
NodeJS succeeded at undermining existing server toolchains, because web devs were easily sold on writing JS for their servers, so tons of successful startups built with Node, and when Node got pretty well established, it was easier to adopt for greenfield projects in the enterprise.
Deno is Node, but better. So it\u2019s not giving a whole market of devs access to a tool that is way easier to write for. It\u2019s marginally easier to manage and you could maybe drop some other toolchain dependencies. But again, those toolchain things are automated/hidden away from developers directly\u2026 like they don\u2019t care we use eslint, they just care CI catches problems before they hit prod and that the linter throws an error early in the process. It\u2019s already easy for them to run locally. So it\u2019s not like Deno lint changes anything about the dev user experience, it just changes what DevOps/platform teams have to manage.","created_at":"2026-03-21T20:42:01Z","created_at_i":1774125721,"objectID":"47471081","parent_id":47468403,"story_id":47467746,"story_title":"404 Deno CEO not found","story_url":"https://dbushell.com/2026/03/20/denos-decline-and-layoffs/","updated_at":"2026-03-22T11:30:16Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"christopherAs"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Hi HN,
Most DevOps tools are good at observing \u2014 they collect data, surface metrics, and send alerts. But the actual decision and action still falls on the engineer.
So I built Riventa.Dev \u2014 a DevOps platform where the AI (Riv) doesn't just surface data, it acts.
What Riv does today:\n- Automatic PR review on every push \u2014 no manual trigger, no GitHub Actions boilerplate\n- Predictive failure detection \u2014 catches patterns that historically cause prod failures\n- DORA metrics dashboard with real pipeline data (MTTR, Deployment Frequency, Change Failure Rate)\n- Security scanning: SAST, SBOM, dependency analysis \u2014 built in, not bolted on\n- Works with GitHub, GitLab, and Bitbucket
Built solo, from scratch, with a focus on keeping things simple for the end user.
What I'd love feedback on: Is the AI-first positioning clear? Where does the UX feel rough?
Free to try \u2014 no credit card required."},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: Riventa.Dev \u2013 AI-native DevOps that acts, not just alerts"},"url":{"matchLevel":"none","matchedWords":[],"value":"https://www.riventa.dev/"}},"_tags":["story","author_christopherAs","story_47351940","show_hn"],"author":"christopherAs","created_at":"2026-03-12T15:17:48Z","created_at_i":1773328668,"num_comments":0,"objectID":"47351940","points":3,"story_id":47351940,"story_text":"Hi HN,
Most DevOps tools are good at observing \u2014 they collect data, surface metrics, and send alerts. But the actual decision and action still falls on the engineer.
So I built Riventa.Dev \u2014 a DevOps platform where the AI (Riv) doesn't just surface data, it acts.
What Riv does today:\n- Automatic PR review on every push \u2014 no manual trigger, no GitHub Actions boilerplate\n- Predictive failure detection \u2014 catches patterns that historically cause prod failures\n- DORA metrics dashboard with real pipeline data (MTTR, Deployment Frequency, Change Failure Rate)\n- Security scanning: SAST, SBOM, dependency analysis \u2014 built in, not bolted on\n- Works with GitHub, GitLab, and Bitbucket
Built solo, from scratch, with a focus on keeping things simple for the end user.
What I'd love feedback on: Is the AI-first positioning clear? Where does the UX feel rough?
Free to try \u2014 no credit card required.","title":"Show HN: Riventa.Dev \u2013 AI-native DevOps that acts, not just alerts","updated_at":"2026-03-12T19:04:08Z","url":"https://www.riventa.dev/"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"jdwithit"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"I got laid off at the end of last year and am currently interviewing for Staff+ DevOps/Platform Engineer type roles. I definitely feel this. I've had a decent flow of recruiter inquiries and had multiple companies go 2-3 rounds of interviews deep with me (not counting the initial "do you have a pulse" recruiter screen calls). Then the communication always seems to dry up and I'm left to wonder what box I failed to check on their hiring rubric.
Semi related, holy hell do companies have a lot of interview rounds these days. It seems pretty standard to spread 5-6 Teams calls over the course of a month. I get that these are high salary, high impact roles and you want to get it right. But this feels really excessive. And I'm not talking about FAANG tech giants here. It's everyone, from startups to random midsize insurance companies."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Tech employment now significantly worse than the 2008 or 2020 recessions"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://twitter.com/JosephPolitano/status/2029916364664611242"}},"_tags":["comment","author_jdwithit","story_47278426"],"author":"jdwithit","children":[47284798],"comment_text":"I got laid off at the end of last year and am currently interviewing for Staff+ DevOps/Platform Engineer type roles. I definitely feel this. I've had a decent flow of recruiter inquiries and had multiple companies go 2-3 rounds of interviews deep with me (not counting the initial "do you have a pulse" recruiter screen calls). Then the communication always seems to dry up and I'm left to wonder what box I failed to check on their hiring rubric.
Semi related, holy hell do companies have a lot of interview rounds these days. It seems pretty standard to spread 5-6 Teams calls over the course of a month. I get that these are high salary, high impact roles and you want to get it right. But this feels really excessive. And I'm not talking about FAANG tech giants here. It's everyone, from startups to random midsize insurance companies.","created_at":"2026-03-06T20:51:45Z","created_at_i":1772830305,"objectID":"47280895","parent_id":47280540,"story_id":47278426,"story_title":"Tech employment now significantly worse than the 2008 or 2020 recessions","story_url":"https://twitter.com/JosephPolitano/status/2029916364664611242","updated_at":"2026-03-09T13:51:54Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tenaka"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"I\u2019m a Senior DevOps / Platform Engineer with about 8 years focused on infrastructure, and a 15 year background in PHP before that. I\u2019ve spent time on both the application and infrastructure sides of production systems, which helps when debugging or designing changes. Over the years I\u2019ve moved deeper into cloud infrastructure, CI/CD, and reliability work \u2014 mostly trying to eliminate recurring failure points instead of layering on quick fixes. I care a lot about long-term system health and building platforms that stay stable as they grow.
Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.com Location: Montreal, QC, Canada\n Remote: Yes. Open to hybrid\n Willing to relocate: No\n Technologies:\n - Infrastructure & Cloud: AWS, GCP, Terraform, Vagrant, Ansible, Packer\n - CI/CD & Automation: Jenkins, Bitbucket Cloud, CI/CD, Git, SVN\n - Programming & Scripting: Python, Bash, PHP, JavaScript, HTML, CSS\n - Testing & Quality: PHPUnit, Behat, Selenium\n - Databases & Cache: MySQL, Redis, Memcache\n - Networking & Security: Nginx, Apache, Cloudflare (WAF, Workers, Zero Trust)\n R\u00e9sum\u00e9/CV: https://docs.google.com/document/d/1DqO7R6gn7YjFTZf3_FpaLc1Hy0cznC-BnFQ8biN_nGI/edit?usp=sharing\n Email: michael@michaeldelle.comThe main thing in this release: skill files. Each project now exposes a skill.md at a predictable URL. You send that URL to any AI bot that can hit REST APIs (I've been using OpenClaw), and it figures out how to clone the repo, push code, create issues all through the API. No extra config, no plugins.
Check this video to see how it works: [https://gisia.dev/docs/ai-bot-skills](https://gisia.dev/docs/ai-bot-skills)
It actually works. That part still surprises me a little.
Happy to answer questions."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Let OpenClaw bot to manage your issues and Git repositories"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://gisia.dev/docs/ai-bot-skills"}},"_tags":["comment","author_okoddcat","story_47215315"],"author":"okoddcat","comment_text":"Hey, just shipped 0.4.0 of [Gisia](https://github.com/gisiahq/gisia), my self-hosted DevOps platform.
The main thing in this release: skill files. Each project now exposes a skill.md at a predictable URL. You send that URL to any AI bot that can hit REST APIs (I've been using OpenClaw), and it figures out how to clone the repo, push code, create issues all through the API. No extra config, no plugins.
Check this video to see how it works: [https://gisia.dev/docs/ai-bot-skills](https://gisia.dev/docs/ai-bot-skills)
It actually works. That part still surprises me a little.
Happy to answer questions.","created_at":"2026-03-02T08:35:48Z","created_at_i":1772440548,"objectID":"47215316","parent_id":47215315,"story_id":47215315,"story_title":"Let OpenClaw bot to manage your issues and Git repositories","story_url":"https://gisia.dev/docs/ai-bot-skills","updated_at":"2026-03-05T23:39:34Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"VioletCranberry"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"I built CocoSearch to fix a problem with code RAG: most tools split source files on token count or character limits, breaking functions and classes across chunk boundaries. The retriever can never return a coherent unit of code.
CocoSearch uses Tree-sitter via https://github.com/cocoindex-io/cocoindex to split at syntax boundaries \u2014 functions, classes, config blocks stay intact. At search time, a second Tree-sitter pass expands matched chunks to enclosing scope boundaries (capped at 50 lines), so results are always self-contained code units.
Search is hybrid: pgvector cosine similarity + PostgreSQL tsvector keyword matching, fused via RRF. Symbol-level filtering (type, name glob) narrows results before fusion.
Where it matters most for DevOps/platform engineers: most code search tools treat YAML, HCL, and Dockerfiles as plain text. Searching "S3 bucket with versioning" across Terraform files returns random line matches because the tool has no concept of a resource block boundary. CocoSearch ships 8 grammar handlers \u2014 GitHub Actions (job/step boundaries), GitLab CI (job/stage boundaries), Docker Compose (service definitions), Helm (chart/template/values), Kubernetes (resource manifests), and Terraform (resource/data blocks). These split infrastructure configs at domain-aware boundaries and extract structured metadata, so search results land on complete, meaningful units. Without grammar handlers, your CI workflow YAML gets chunked on whitespace like any other text file. The grammar system is extensible \u2014 copy a template, define path patterns and separators, it gets autodiscovered.
The dependency graph covers the same territory: Python, JS/TS, Go, plus Docker Compose (image refs, depends_on, extends), GitHub Actions (uses action/workflow refs, needs inter-job deps), GitLab CI (include, extends, needs, trigger pipelines), Terraform (module sources, required_providers, remote_state), and Helm (template includes, Chart.yaml subcharts). Forward trees, reverse impact analysis, and dependency-enriched search results.
One thing I'm particularly happy with: a Markdown extractor tracks references from documentation to source files (inline links, code spans, frontmatter depends: fields). During PR review, impact analysis flags docs that reference changed files \u2014 so "you renamed cli.py but docs/architecture.md and CLAUDE.md still link to it" surfaces automatically instead of relying on reviewers to notice.
Stack: PostgreSQL 17 + pgvector, Ollama for local embeddings (optional OpenAI/OpenRouter), CocoIndex, Tree-sitter. Runs as CLI, MCP server, web dashboard, or REPL. 32 languages, 8 grammar handlers, 10 dependency extractors. MIT licensed.
Happy to answer questions about the chunking approach, grammar handlers, or anything else."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: CocoSearch \u2013 semantic code search with syntax-aware chunking"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://github.com/VioletCranberry/coco-search"}},"_tags":["comment","author_VioletCranberry","story_47196312"],"author":"VioletCranberry","comment_text":"I built CocoSearch to fix a problem with code RAG: most tools split source files on token count or character limits, breaking functions and classes across chunk boundaries. The retriever can never return a coherent unit of code.
CocoSearch uses Tree-sitter via https://github.com/cocoindex-io/cocoindex to split at syntax boundaries \u2014 functions, classes, config blocks stay intact. At search time, a second Tree-sitter pass expands matched chunks to enclosing scope boundaries (capped at 50 lines), so results are always self-contained code units.
Search is hybrid: pgvector cosine similarity + PostgreSQL tsvector keyword matching, fused via RRF. Symbol-level filtering (type, name glob) narrows results before fusion.
Where it matters most for DevOps/platform engineers: most code search tools treat YAML, HCL, and Dockerfiles as plain text. Searching "S3 bucket with versioning" across Terraform files returns random line matches because the tool has no concept of a resource block boundary. CocoSearch ships 8 grammar handlers \u2014 GitHub Actions (job/step boundaries), GitLab CI (job/stage boundaries), Docker Compose (service definitions), Helm (chart/template/values), Kubernetes (resource manifests), and Terraform (resource/data blocks). These split infrastructure configs at domain-aware boundaries and extract structured metadata, so search results land on complete, meaningful units. Without grammar handlers, your CI workflow YAML gets chunked on whitespace like any other text file. The grammar system is extensible \u2014 copy a template, define path patterns and separators, it gets autodiscovered.
The dependency graph covers the same territory: Python, JS/TS, Go, plus Docker Compose (image refs, depends_on, extends), GitHub Actions (uses action/workflow refs, needs inter-job deps), GitLab CI (include, extends, needs, trigger pipelines), Terraform (module sources, required_providers, remote_state), and Helm (template includes, Chart.yaml subcharts). Forward trees, reverse impact analysis, and dependency-enriched search results.
One thing I'm particularly happy with: a Markdown extractor tracks references from documentation to source files (inline links, code spans, frontmatter depends: fields). During PR review, impact analysis flags docs that reference changed files \u2014 so "you renamed cli.py but docs/architecture.md and CLAUDE.md still link to it" surfaces automatically instead of relying on reviewers to notice.
Stack: PostgreSQL 17 + pgvector, Ollama for local embeddings (optional OpenAI/OpenRouter), CocoIndex, Tree-sitter. Runs as CLI, MCP server, web dashboard, or REPL. 32 languages, 8 grammar handlers, 10 dependency extractors. MIT licensed.
Happy to answer questions about the chunking approach, grammar handlers, or anything else.","created_at":"2026-02-28T15:23:02Z","created_at_i":1772292182,"objectID":"47196352","parent_id":47196312,"story_id":47196312,"story_title":"Show HN: CocoSearch \u2013 semantic code search with syntax-aware chunking","story_url":"https://github.com/VioletCranberry/coco-search","updated_at":"2026-03-05T23:39:16Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"wahnfrieden"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Looking for contract or consulting work. I do end-to-end software development (native iOS and macOS in particular, as well as backend and scalability). I can solve dev velocity challenges and implement Continuous Deployment. I can also overhaul QA and production health practices within organizations by working directly with teams and management (across engineering, product, support).
Location: Toronto\n Remote: yes\n Willing to relocate: no (but I am a dual CA/US citizen and am frequently in NYC)\n Technologies: Apple native development (SwiftUI, UIKit, AppKit), Python, Django, Postgres, devops tools. Scalability and high availability and dev velocity focused skill set, besides the mobile dev work. I am proficient with OpenAI Codex for assisted coding (I understand how to review its work and direct the architecture) and am perfectly capable of manual coding/debugging too.\n R\u00e9sum\u00e9/CV: N/A at the moment (contact me for it) but I built and scaled the backend for DrawQuest (top 10 iPad/iOS app), directed teams (devops, platform, full stack, mobile) at Top Hat for 8 years, and independently built this iOS app business the last few years: https://reader.manabi.io\n Email: hn at manabi io Location: Toronto\n Remote: yes\n Willing to relocate: no (but I am a dual CA/US citizen and am frequently in NYC)\n Technologies: Apple native development (SwiftUI, UIKit, AppKit), Python, Django, Postgres, devops tools. Scalability and high availability and dev velocity focused skill set, besides the mobile dev work. I am proficient with OpenAI Codex for assisted coding (I understand how to review its work and direct the architecture) and am perfectly capable of manual coding/debugging too.\n R\u00e9sum\u00e9/CV: N/A at the moment (contact me for it) but I built and scaled the backend for DrawQuest (top 10 iPad/iOS app), directed teams (devops, platform, full stack, mobile) at Top Hat for 8 years, and independently built this iOS app business the last few years: https://reader.manabi.io\n Email: hn at manabi ioI used to love my job (DevOps, Platform, DevSecOps Engineer) but I learned the hard way to disappear after 4:59PM and never get online before 8:59
Also, no more e-mail, teams, slack, etc, on my personal phone.\nWhile working be in the office or WFH, I do my best but outside that, you won't find me.
I am addicted to being useful culture died in early 2000s....\nI am seeing projects where the goal is to have AI Teams managing AI Teams without human intervention, so enjoy your life and take workplace less seriously, we are gonna be replaced and you will regret spending more time working than living!!"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"I'm addicted to being useful"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://www.seangoedecke.com/addicted-to-being-useful/"}},"_tags":["comment","author_h4kunamata","story_46690402"],"author":"h4kunamata","children":[46700232],"comment_text":"The problem of doing this now is that no company will care, they will be happy that you are doing more for less, so no salary increase, no job tittle change.
I used to love my job (DevOps, Platform, DevSecOps Engineer) but I learned the hard way to disappear after 4:59PM and never get online before 8:59
Also, no more e-mail, teams, slack, etc, on my personal phone.\nWhile working be in the office or WFH, I do my best but outside that, you won't find me.
I am addicted to being useful culture died in early 2000s....\nI am seeing projects where the goal is to have AI Teams managing AI Teams without human intervention, so enjoy your life and take workplace less seriously, we are gonna be replaced and you will regret spending more time working than living!!","created_at":"2026-01-20T22:12:39Z","created_at_i":1768947159,"objectID":"46698404","parent_id":46690402,"story_id":46690402,"story_title":"I'm addicted to being useful","story_url":"https://www.seangoedecke.com/addicted-to-being-useful/","updated_at":"2026-03-05T23:29:26Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"ramkumarvenkat"},"title":{"matchLevel":"none","matchedWords":[],"value":"Sei (YC W22) Is Hiring a DevOps Engineer (India/In-Office/Chennai/Gurgaon)"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"https://www.ycombinator.com/companies/sei/jobs/Rn0KPXR-devops-platform-ai-infrastructure-engineer"}},"_tags":["job","author_ramkumarvenkat"],"author":"ramkumarvenkat","created_at":"2026-01-14T01:01:12Z","created_at_i":1768352472,"objectID":"46610967","title":"Sei (YC W22) Is Hiring a DevOps Engineer (India/In-Office/Chennai/Gurgaon)","updated_at":"2026-03-05T23:23:16Z","url":"https://www.ycombinator.com/companies/sei/jobs/Rn0KPXR-devops-platform-ai-infrastructure-engineer"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"Bral1232"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Hey everyone!
I built CILens, a CLI tool for analyzing GitLab CI/CD pipelines and finding optimization opportunities.
Check it out here: https://github.com/dsalaza4/cilens
I've been using it at my company and it's given me really valuable insights into our pipelines\u2014identifying slow jobs, flaky tests, and bottlenecks. It's particularly useful for DevOps, platform, and infra engineers who need to optimize build times and improve CI reliability.
What it does:
- Fetches pipeline & job data from GitLab's GraphQL API
- Groups pipelines by job signature (smart clustering)
- Shows P50/P95/P99 duration percentiles instead of misleading averages
- Detects flaky jobs (intermittent failures that slow down your team)
- Calculates time-to-feedback per job (actual developer wait times)
- Ranks jobs by P95 time-to-feedback to identify highest-impact optimization targets
- Outputs human-readable summaries or JSON for programmatic use
Key features:
- Written un Rust for maximum performance
- Intelligent caching (~90% cache hit rate on reruns)
- Fast concurrent fetching (handles 500+ pipelines efficiently)
- Automatic retries for rate limits and network errors
- Cross-platform (Linux, macOS)
Currently supports GitLab only, but the architecture is designed to support other CI/CD providers (GitHub Actions, Jenkins, CircleCI, etc.) in the future.
Would love feedback from folks managing large GitLab instances!"},"story_title":{"matchLevel":"none","matchedWords":[],"value":"CILens \u2013 CI/CD Pipeline Analytics for GitLab"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://github.com/dsalaza4/cilens"}},"_tags":["comment","author_Bral1232","story_46529380"],"author":"Bral1232","comment_text":"Hey everyone!
I built CILens, a CLI tool for analyzing GitLab CI/CD pipelines and finding optimization opportunities.
Check it out here: https://github.com/dsalaza4/cilens
I've been using it at my company and it's given me really valuable insights into our pipelines\u2014identifying slow jobs, flaky tests, and bottlenecks. It's particularly useful for DevOps, platform, and infra engineers who need to optimize build times and improve CI reliability.
What it does:
- Fetches pipeline & job data from GitLab's GraphQL API
- Groups pipelines by job signature (smart clustering)
- Shows P50/P95/P99 duration percentiles instead of misleading averages
- Detects flaky jobs (intermittent failures that slow down your team)
- Calculates time-to-feedback per job (actual developer wait times)
- Ranks jobs by P95 time-to-feedback to identify highest-impact optimization targets
- Outputs human-readable summaries or JSON for programmatic use
Key features:
- Written un Rust for maximum performance
- Intelligent caching (~90% cache hit rate on reruns)
- Fast concurrent fetching (handles 500+ pipelines efficiently)
- Automatic retries for rate limits and network errors
- Cross-platform (Linux, macOS)
Currently supports GitLab only, but the architecture is designed to support other CI/CD providers (GitHub Actions, Jenkins, CircleCI, etc.) in the future.
Would love feedback from folks managing large GitLab instances!","created_at":"2026-01-07T17:31:36Z","created_at_i":1767807096,"objectID":"46529381","parent_id":46529380,"story_id":46529380,"story_title":"CILens \u2013 CI/CD Pipeline Analytics for GitLab","story_url":"https://github.com/dsalaza4/cilens","updated_at":"2026-03-05T23:18:25Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"mraza007"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Location: New York City, United States
Remote: Yes (Preferred)
Willing to relocate: No
Technologies: AWS (ECS, EKS, Lambda, CloudFormation, CDK, Glue, MWAA), Terraform, Python, GitHub Actions, GitLab CI, Jenkins, Docker, Kubernetes, PostgreSQL, FastAPI, Flask, Django, Bash, Linux
R\u00e9sum\u00e9/CV: Available upon request
Email: muhammadraza0047@gmail.com
GitHub: https://github.com/mraza007
Website: https://muhammadraza.me/work
I'm a Senior DevOps Engineer with 5 years of experience in cloud infrastructure and automation. I spent 2 years at AWS Professional Services, where I led CloudFormation Resources Migration, built CDK constructs in Python and TypeScript, and helped enterprise customers design CI/CD pipelines.
I'm open to DevOps, platform engineering, SRE, or backend Python roles. Happy to chat about contract or full-time opportunities."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Who wants to be hired? (January 2026)"}},"_tags":["comment","author_mraza007","story_46466073"],"author":"mraza007","comment_text":"Location: New York City, United States
Remote: Yes (Preferred)
Willing to relocate: No
Technologies: AWS (ECS, EKS, Lambda, CloudFormation, CDK, Glue, MWAA), Terraform, Python, GitHub Actions, GitLab CI, Jenkins, Docker, Kubernetes, PostgreSQL, FastAPI, Flask, Django, Bash, Linux
R\u00e9sum\u00e9/CV: Available upon request
Email: muhammadraza0047@gmail.com
GitHub: https://github.com/mraza007
Website: https://muhammadraza.me/work
I'm a Senior DevOps Engineer with 5 years of experience in cloud infrastructure and automation. I spent 2 years at AWS Professional Services, where I led CloudFormation Resources Migration, built CDK constructs in Python and TypeScript, and helped enterprise customers design CI/CD pipelines.
I'm open to DevOps, platform engineering, SRE, or backend Python roles. Happy to chat about contract or full-time opportunities.","created_at":"2026-01-02T20:09:36Z","created_at_i":1767384576,"objectID":"46468821","parent_id":46466073,"story_id":46466073,"story_title":"Ask HN: Who wants to be hired? (January 2026)","updated_at":"2026-03-05T23:18:07Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"wahnfrieden"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["devops","platform"],"value":"Looking for contract or consulting work. I can do development (iOS, macOS, web). I can solve dev velocity challenges and implement Continuous Deployment. And I can overhaul QA and production health practices within organizations by working directly with teams and management.
Location: Toronto\n Remote: yes\n Willing to relocate: no (but I am a US citizen and am frequently in NYC)\n Technologies: Apple native development (SwiftUI, UIKit, AppKit), Python, Django, Postgres, devops tools. Scalability and high availability and dev velocity focused skill set, besides the mobile dev work. I am proficient with OpenAI Codex for assisted coding (I understand how to review its work and direct the architecture) and am perfectly capable of manual coding/debugging too.\n R\u00e9sum\u00e9/CV: N/A at the moment (contact me for it) but I built and scaled the backend for DrawQuest (top 10 iPad/iOS app), directed teams (devops, platform, full stack, mobile) at Top Hat for 8 years, and independently built this iOS app business the last few years: https://reader.manabi.io\n Email: hn at manabi io Location: Toronto\n Remote: yes\n Willing to relocate: no (but I am a US citizen and am frequently in NYC)\n Technologies: Apple native development (SwiftUI, UIKit, AppKit), Python, Django, Postgres, devops tools. Scalability and high availability and dev velocity focused skill set, besides the mobile dev work. I am proficient with OpenAI Codex for assisted coding (I understand how to review its work and direct the architecture) and am perfectly capable of manual coding/debugging too.\n R\u00e9sum\u00e9/CV: N/A at the moment (contact me for it) but I built and scaled the backend for DrawQuest (top 10 iPad/iOS app), directed teams (devops, platform, full stack, mobile) at Top Hat for 8 years, and independently built this iOS app business the last few years: https://reader.manabi.io\n Email: hn at manabi io