lawnchair
Joined 16 years ago
Karma
313
Submissions
78
Member since
Aug 3
Building Terrateam
View on Hacker NewsRecent submissions
Comment · 2 months ago
> Our field has a weird relationship with terminal and command line interfaces. The time has come to re-evaluate it.
I like chocolate I like vanilla
Comment · 11 months ago
I have to say that if an incident becomes so overwhelming that nobody can spare even a moment to communicate with customers, that points to a deeper operational problem. A status page is not something you update only when things are calm. It is part of the response itself. It is how you keep users informed and maintain trust when everything else is going wrong.
If communication disappears entirely during an outage, the whole operation suffers. And if that is truly how a company handles incidents, then it is not a practice I would want to rely on. Good operations teams build processes that protect both the system and the people using it. Communication is one of those processes.
Comment · 1 year ago
We're still figuring out what balance makes sense between openness and sustainability, and we'd rather take the time to get it right than rush into a license we'll regret later. The goal is for Stategraph to last a long time.
Comment · 1 year ago
Definitely agree. Most teams don't choose a language for purely rational reasons, and we're not pretending we did.
We like OCaml, it makes us excited to build. We know the language deeply, which means we can reason about performance and behavior before we run the code. We can onboard new engineers quickly because the type system forces clarity.
The runtime is simple enough that we can predict what it's doing. So yes, part of it is that OCaml feels good to use. But that feeling comes from years of watching it make complex systems simpler to reason about, not harder.
Comment · 1 year ago
Finding good candidates is easy.
Comment · 1 year ago
We already made it. Thanks for the callout.
Comment · 1 year ago
Terrateam | Remote (EU/US timezones) | Full-time | OCaml
Terrateam builds GitOps automation for Terraform and OpenTofu. We help large engineering teams plan, review, and apply infrastructure changes safely, directly from GitHub and GitLab pull/merge requests.
We are looking for a Software Engineer who can move between backend systems, infrastructure, and open source tooling. You'll work on Terrateam's OCaml core, support customers, and contribute to the design of next-generation Terraform orchestration.
You might be a good fit if you:
- Care about correctness and reliability in complex systems
- Have experience with infrastructure automation, CI/CD, or compilers
- Enjoy working in OCaml or another strongly typed functional language
- Value autonomy and precision in engineering
Stack: OCaml, Postgres, Docker
Team: small, remote, and technical
Comp: €90k–€130k depending on experience
We are based in Amsterdam and work async across EU and US time zones. Preference for EU timezones.
Apply: https://terrateam.io/careers
Comment · 1 year ago
Using another company's funding announcement to shill your own is lame.
Comment · 1 year ago
Terraform Cloud does not actually solve this. It moves the state into their service and manages locking centrally, but the underlying model is unchanged. It is still one file with a global lock. That is why refresh bottlenecks and contention show up there too. What we are pointing at is the model itself, not just where the file is hosted. We know this space well from building Terrateam, which competes with Terraform Cloud on orchestration.
Comment · 1 year ago
Hi Alex. Great question and definitely something top of mind as we build Stategraph. The short answer is there is always a service layer in front of the database. Users and teams interact with that service, not the database directly. That is where access control and ownership boundaries live.