russell_h
If a hyperscaler wants to connect a 500MW datacenter, great. That's a huge investment, with various positive externalities. Requiring the builders of the datacenter to also pay for whatever transmission, substations and generation upgrades their demand requires is just not that big of a deal compared to the total size of the investment, which is part of why companies like Microsoft and Anthropic have committed to doing just this.
The article notes that some states are already moving to require this, and more should do the same.
There's a huge opportunity here; the AI buildout is probably the biggest wave of private industrial investment in decades, if not ever, and it comes at a time that we need to accelerate the buildout of our electrical grid. Let's have the hyperscalers pay for it in a way that makes this positive sum for everyone.
As an aside, it's kind of funny that this article reads like it was written by Claude.
Why not? Do you trust AWS with things that need to be private?
Back when I was an OSU student I taught myself a lot about practical systems programming, and I was consulting Beej's Guide to Network Programming daily. I kept lamenting to myself that I wished the expensive university was proving as useful as this guy's free website.
Awesome that it has come full circle, great hire by someone.
We launched support today for C1 to act as an EMA identity provider (we mint the short-lived scoped tokens), so I'm excited to hook this up for Linear and some of the other MCPs we use, and get out of the business of constant OAuth flows. Claude has been doing this magically for some of their built-in connectors (at least Slack I think) and the experience is pretty great.
Disclosure: VPE at C1. We wrote up how we’re approaching it here if anyone’s in the weeds on this: https://www.c1.ai/docs/product/admin/enterprise-managed-auth...
ConductorOne is building the platform for identity security and least privilege automation — helping companies secure access to everything, without slowing people down. Our engineering culture emphasizes small, high-ownership teams that deliver measurable impact and move quickly.
We’re hiring across many areas:
- Software Engineers – We’re growing our product development teams in SF and Portland.
- Site Reliability Engineering – We’re looking for SREs and a hands-on SRE manager (SF or Portland) to own reliability, performance, and infrastructure as we scale.
- Forward Deployed Engineering (FDE) – We’re building a brand-new customer-facing engineering org: we're looking for engineers who want to work closely with customers to modernize and automate identity operations, and a Manager, FDE to lead the team.
- Governance, Risk & Compliance (GRC) – We’re building a new GRC function and hiring our first Compliance Engineer to help scale our security and audit programs.
We work primarily in Go and TypeScript, on AWS + Kubernetes.Apply here: https://www.conductorone.com/careers
To be clear though, this grant is for over $1,200 per ton.
It says they're preventing 15,000 tons of emissions, but there are all kinds of ways to prevent or offset greenhouse gas emissions for under $10/ton. So at a glance this project appears to be allowing almost 2 million tons in preventible emissions in order to... pay people to bike around and collect food scraps?
Edit: also, school quality.
At risk of harping on a tired topic, have you thought about embedding an AI query generator? For ad-hoc queries like I mostly use DuckDB for I’ve found it’s almost always fastest for me to paste the schema to ChatGPT, tell it what I’ll looking for, then paste the response back into the DuckD CLI, but the whole process isn’t very ergonomic.
I think I’m sort of after duckbook.ai, but with access to a local duckdb.
ConductorOne (https://conductorone.com) is a modern identity governance platform built to secure and simplify access management for today’s fast-changing, cloud-based environments. We unify access and permissions data from across all your cloud, infrastructure, and on-prem tools, giving real-time visibility and control, and help our customers reduce identity risks, automate access reviews, and streamline access requests, with powerful automation and user-friendly experiences. Trusted by teams at DigitalOcean, Instacart, Ramp, and more.
We use lots of Go, React, Temporal, gRPC, DynamoDB, Postgres and AWS. We’re looking for product-minded engineers, who love taking ownership of the product and shipping every day.
Frontend Engineer (SF preferred): https://jobs.ashbyhq.com/conductorone/01862e6d-0d75-43da-8fc...
Go Engineer (Portland, SF, Remote (US)): https://jobs.ashbyhq.com/conductorone/7a164d64-6427-4fba-b71...
Apply directly via the links above and mention this post, or reach out via the email in my profile.
https://youtube.com/watch?v=V3A6L2Dao6s
Great idea, I hope it works.
In practice though there are a lot of advantages to having approximately-time-ordered IDs, and I’ve found the pitfalls easy enough to avoid.
* Far better isolation than a normal Linux container * If WASM takes off, maybe architecture-independent artifact distribution * If WASM takes off, maybe improved ability to call from one language into another
As a Kubernetes container runtime WASM today is probably most comparable to gVisor, with the somewhat huge caveat that it prevents you from just running normal Linux software.