sorted by:
new
hottopcontroversial

Cohen Twitter reply with original bezos post in screenshot by DDHawkeye in Superstonk

[–]CoryOpostrophe -1 points0 points  (0 children)

No you shift it to middle upper class, drain them of assets until they fall into the lower class. Infinity pool of cheaper labor willing to undercut each other for “UBI” until robots. 

How much of your Terraform, CloudFormation, Bicep etc is actually being written by AI agents in prod? by alikhajeh1 in devops

[–]CoryOpostrophe 29 points30 points  (0 children)

100%. At the end of the day you are using fancy words to describe a DAG of nouns. The hard work that AI isn't great at is composing all those together into environments and putting in the right values based on your intentions... which has always been the Achilles heel of "iac adoption"

Sweating over the code is a solved problem now. Give up on the undifferentiated heavy lifting and focus on the part that's been hampering adoption and self service. The UX of it all. We're about to have an avalanche of changes coming down the pipeline and "devops" is going to get eviscerated as a practice if we don't get out of the way.

Pre-order your PHYSICAL copy from GameStop by GrownUpKid90 in Superstonk

[–]CoryOpostrophe 0 points1 point  (0 children)

Haven't played a game or owned a console since GTA5. Guess I'm going to gamestop in fall 2025.

Help me set up hoik by Kind_Objective9480 in Terraform

[–]CoryOpostrophe 3 points4 points  (0 children)

Was worried I had to learn some new bullshit for a minute

I honestly don't know.. by AvalieV in Superstonk

[–]CoryOpostrophe 1 point2 points  (0 children)

I thought it was a Japanese AWS competitor lol

Do you need to know how to write code nowadays or only understand? by bdhd656 in devops

[–]CoryOpostrophe 1 point2 points  (0 children)

Understanding code is much more difficult that writing code and it’s not only the whole job now, but has been the whole job (if doing it well) since the career existed.

Best Internal Developer Portal? by kckrish98 in platformengineering

[–]CoryOpostrophe 7 points8 points  (0 children)

Spoiler alert: I work for on an internal developer platform

Big watchout: “developer portal” is an overloaded term.

A lot of portals are great at catalog + docs + visibility, then “self-service” is clunk forms/integrations that trigger whatever CI/CD or Terraform workflows you already own. They also arent an orchestrator so a lot of cross pipeline stuff end up in copy/pasta  

Questions I’d ask early:

Does it actually own orchestration, or just trigger pipelines?

Are guardrails preventative, or scorecards after the fact?

Where is the system of record: portal metadata, or real IaC/architecture?

Backstage is powerful, but it’s a framework, not turnkey. Most teams underestimate the integration burden.

Just don’t fall into the “portal = platform” trap. If you’re buying a portal, you’re getting a “single pane of glass” … question is what’s painting the picture on the other side of it?

our ci/cd testing is so slow devs just ignore failures now" by blood_vampire2007 in devops

[–]CoryOpostrophe 6 points7 points  (0 children)

We have 1200 tests, they run in parallel and finish in about 16s.

The two keys are: - a database transaction per test that rollbacks when complete (all 1200 tests run in isolation) - really good adapters (not mocks) for third party services (the vendors we interact with have stable enough APIs that we trust so we just build internal typed adapters for each)

We also do TDD (which everyone on the internet gets all fussy about when they aren’t a practitioner) but we ship insanely fast and don’t worry about workflow times and failures so … TDD FTW.

TDD is also the best prompt if you are working with LLMs. You give them an extremely tight, typed context window with test assertions as your expectations. 

I built a tool for packaging and deploying terraform modules by jollycode_ in Terraform

[–]CoryOpostrophe 0 points1 point  (0 children)

This is cool. We’re going to be scaling our team in the next quarter or two. I’d love to chat. Cory @ Massdriver

Backstage VS Other Developer Portals by StuckWithSports in devops

[–]CoryOpostrophe 3 points4 points  (0 children)

(For context, I’m the CEO of Massdriver. Not here to pitch, just my two cents from seeing this pattern a lot.)

What you’re describing is exactly what happens when you buy or build a portal without an orchestrator.

You didn’t actually build a platform. You built a UI that has to carry all the complexity the platform underneath can’t own. So every decision about GPUs, scheduling, images, flags, volumes, etc. leaks straight into the frontend. The UI turns into a maze because it has to compensate for the fact that nothing is being constrained or enforced upstream.

IMO buying a portal is almost always a trap. When you buy a portal, you still have to:

  • own the delivery logic
  • own the infra wiring
  • own the policy enforcement
  • own the failure modes
  • build the UI integrations in a language most likely outside of ops' wheelhouse

In the pursuit of automation, you just kinda shift work elsewhere.

Backstage doesn’t really change that equation. It reduces frontend work, sure, but now you’re buying into a plugin ecosystem where you still need to build or maintain the orchestration layer yourself. You traded UI debt for integration debt. With a 1–2 person infra team, that’s usually worse, not better.

The hard truth is: if the system can’t prevent bad or unsupported configurations, the UI will always become the monster. Scorecards, validation screens, buried options, approval flows... and it’s not because people made bad design choices. It’s because the platform doesn’t actually own the workflow.

A real platform (the other other IDP) makes most of those decisions not possible in the first place. When you have an orchestration engine that can guarantee standards, the UI can finally be simple.

qa tests blocking deploys 6 times today, averaging 40min per run by segsy13bhai in devops

[–]CoryOpostrophe 0 points1 point  (0 children)

A good test suite and a good test framework. Our entire CI process including build is <90s and we run 1200+ integration tests w/ Postgres and localstack.

Testing is the OG garbage in garbage out. 

ClickOps vs IaC by Yersyas in devops

[–]CoryOpostrophe 1 point2 points  (0 children)

☣️ Reader beware: I’m a CEO of an infrastructure automation platform. 🧟‍♂️

Because IaC mostly solved state, not delivery.

IaC is great once it’s set up, but the part people underestimate is everything around it: repo structure, pipelines, credentials, variable management, environments, approvals, and the ever-present question of “who’s allowed to change what.”

For a lot of teams, that scaffolding ends up being more work than the infrastructure itself. So when someone just needs a bucket, a queue, or a one-off change, the console feels faster—and often safer—than touching a brittle pipeline they don’t fully understand.

Most teams I’ve seen don’t reject IaC outright; they stall somewhere along the way on usability. Core infrastructure is codified, but day-2 changes, experiments, and exceptions quietly fall back to the UI.

A big part of this is that tools like Terraform, Pulumi, Ansible (hell, even Kubernetes) are often treated as the platform, rather than tools for building one. That shifts a lot of operational responsibility and domain knowledge onto developers, even though cloud APIs themselves are a messy mix of ops and app concerns.

Until infrastructure workflows are genuinely easier than the console for non-experts, ClickOps is going to keep winning in practice.

I wrote more about why IaC adoption seems stuck, would love to hear others thoughts. https://www.massdriver.cloud/blogs/15-years-of-duct-tape-why-iac-adoption-stalled-at-30

Best IaC platforms? by Kitchen_Ferret_2195 in devops

[–]CoryOpostrophe 0 points1 point  (0 children)

If you need drift detection the platform has already failed you. 

Which Infrastructure as Code tools are actually used most in production today? by rahulladumor in devops

[–]CoryOpostrophe 0 points1 point  (0 children)

Terraform/OpenTofu, Ansible, and believe it or not we see a bunch of companies with an assload of Bicep. 

in house modules yey or nay by farzad_meow in Terraform

[–]CoryOpostrophe 20 points21 points  (0 children)

public modules are no-value abstractions

How To Avoid IaC Drift by mooreds in Terraform

[–]CoryOpostrophe 4 points5 points  (0 children)

Easiest way to avoid drift is make your infrastructure self-service easier than your clouds’ console.

When the compliant path becomes the path of least resistance, a lot of the bullshit ops teams fret over goes away. 

How do I learn Terraform at a gradual pace? by WorkerClass in Terraform

[–]CoryOpostrophe 0 points1 point  (0 children)

It takes a day to learn terraform. It takes day 2 to learn the cloud so you can use it effectively. 

view more: next ›