Review AI-generated Markdown and HTML in a focused workspace Discussion | Link

Feel free to include any brands or product names as well. Be as obscure or on the nose as you'd like....

Turn any idea into a motion video Discussion | Link

Mach's approach differs sharply from some of its peers.

A visual walkthrough of how io_uring works: shared rings, SQEs/CQEs, batching, SQPOLL, multishot operations, linked operations, fixed/provided buffers, and the tradeoffs that come with exposing such a powerful linux kernel interface. submitted by /u/Ok_Marionberry8922 [link] [留言]

AI makes us faster, but does it make us better engineers, or just more dependent? As a follow-up...

submitted by /u/mttd [link] [留言]

Over the past year, I've noticed something interesting in conversations about enterprise AI. Most...

https://xcancel.com/LarsAnders1620/status/206820886474754051...

Most of use here are wage earners. I keep hearing of people making money with interesting side hustles. Like my neighbour rents graduation gowns for the local university. I'd love to find something like that but I need inspiration.

TL;DR: I built a .NET library that renders Helm charts and drives Kubernetes releases without shelling out to the helm CLI. 129/129 templates across ingress-nginx, cert-manager, external-dns, podinfo, and metrics-server now render successfully. The main entry point is HelmSharp.Action, with lower-level packages available for chart loading, rendering, Kubernetes operations, and release storage. MIT licensed, looking for feedback and early adopters. Why I Built This At work, our .NET services deploy to Kubernetes through Helm. Every Docker image had to bundle the helm binary — another dependency to manage, another layer in the image, another surface for CVEs. I wanted to cut that out entirely and do Helm-style rendering directly in-process. The .NET ecosystem doesn't really have this. There are YAML libraries. There are Kubernetes client libraries. There are template engines. But nothing ties them together the way helm template does — values merging, named templates, include , range , toYaml , the whole Sprig function set, all wired into a single render pipeline. So I started building one. (This is also my first real open source project — I'd spent years consuming OSS without contributing back, and HelmSharp is what came out of deciding to change that.) What HelmSharp Does HelmSharp is a multi-package .NET SDK (net8.0 / net9.0 / net10.0) that covers: Package What it does HelmSharp.Action High-level Helm client — TemplateAsync , UpgradeInstallAsync , RollbackAsync HelmSharp.Chart Chart loading from directories and .tgz , values merging, --set / --set-json style overrides HelmSharp.Engine Helm-style template rendering — 100+ Sprig/Helm functions HelmSharp.Kube Kubernetes apply, delete, and wait (no kubectl needed) HelmSharp.Release Release history stored in Kubernetes Secrets (Helm-compatible) HelmSharp.Repo Chart repository index, pull, and search Plus Registry , Storage , PostRenderer extension points Here's the lower-level rendering API — no result objects, no stdout

Let agents deploy before signup Discussion | Link