etxm

You’ve gotta check out Charm’s tools for CLI/TUI dev. They are doing some great work.

https://charm.sh/

Test it?! I develop it on a crappy laptop!

Wait until they see how awful IaC is.

Those lakes are going to be a real bitch when belters hit these rings with an EMP.

At my first startup we used XMPP (wildfire?) to do a lot of our ops work.

All of our pet servers had a background process sitting in a chat room.

We did deploys, restarted process, got alerts, and a whole bunch of other stuff all via XMPP.

It was much cooler than our product that never made any money :)

A metaverse is the last thing on earth this planet needs.

> We believe building “Instagram Kids” is the right thing to do

No it’s fucking not, you morally corrupt sacks of garbage.

Kids need social networks, but they need them IRL.

Instagram and Facebook are a scourge.

Honest question: Besides IT endpoint management, why does our industry continue to develop software that is leaning more and more towards containerization on Mac OS?

I’ve been a Mac user for 20 years and do a lot of docker and Kubernetes work. I recently started developing on a Linux machine that was a fourth of the price and a lot less burden for my day-to-day work.

Would you meet with them? They’ve invested millions in a competitor.

Aside: is the username an Expanse reference?

Thanks for the reply. This is some great feedback. Our deck definitely has some future features and strategies in it, so if I go forward with the call I’ll definitely need to do some trimming down

This is all new to me so I’m not exactly sure what makes a firm large. There are 50 companies give or take in their portfolio. Less than 1b in the fund.

Depending on how much memory the rules take up you could use SSE in the server SDK. I believe that’s how LaunchDarkly works.

https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...

I had an offer in December that was 33/33/22/11

Fuck both of these companies.

Wait until you hear someone noun “solve,” it’s the most infuriating sound to leave a PMs mouth.

I’m hoping we can come to an agreement during this meeting to find the solve.

Would ___ work for this solve?

So much this. “Let it crash” is cargo culted too hard IMO. If a caller (being another library or end user) can be given information to correct an error, give it!

Let it crash works well for a phone system where it doesn’t make sense to call both parties back if the thing failed.

Oh for sure, that’s point #4, but at least it’s in the same apply.

In #1 there is also a tight coupling between two different sources. If team A changes their output, the dependent team B's references break.

Also 1.2: security. If I can read an attribute from your state file, I can read the whole thing.

People tend to complain about HCL a lot, I think it’s a great language for infrastructure. I don’t want a “real programming language” for provisioning infrastructure. I feel like every time I’ve seen someone “need” a real programming language, that there is a _better_ way to do the task at hand with HCL.

That being said, there are some ugly bits.

1. Remote state as a data source means your infra is broken, you just don’t know it yet. Two apply’s have to occur to get your infra in the correct state, but they are separated by an arbitrary amount of time between executions. Even if you automate it with CI/CD, your second root module could be broken until run since it depends on the output of the other module.

2. Public modules are absolute garbage. Go find the best one, it’s trash. Here is why, 10-20 orgs all come in and tweak the module to work for them. You’ll often see 1-10 resources in a module (sometimes more), but the module will end up with more _input complexity_ than the underlying resources. Sometimes even more inputs than all the original resources combined! In the end, you get a module that “works” for everyone, with a half baked “DRY abstraction” for N number of organizations.

3. Organizing code is hard, because we often don’t fully consider environments/workspaces, infrastructure ownership, change management, and other sociotechnical concerns. I think Terraform and IaC in general is the epitome of Conway’s Law and when the (changing) social structure of the organization isn’t followed, the code gets harder to work with. This point is at odds with #1 above.

4. People tend to think “terraform apply” is a magic transactional boundary around your infrastructure. If it applies, it worked!!! But in reality, if modules aren’t crafted correctly they can “apply” cleanly, but still introduce an outage while they are executing.

All that said, I’m excited for the 1.0 release. I love terraform. Thanks to all (except module authors) for the hard work.

> Also the staticness of providers are a serious pain, for example you can't create a kubernetes cluster then add a resource to it.

TF def has some rough edges, but you can certainly create a cluster and add resources in a single root module (I don’t think it’s a great practice).

In this example the EKS cluster is in a module, but it can be a ref to a resource in the same module as well.

  data "aws_eks_cluster_auth" "current" {
    name = module.eks.cluster_id
  }

  provider "kubernetes" {
    load_config_file       = false
    host                   = module.eks.cluster_endpoint
    cluster_ca_certificate = base64decode(module.eks.cluster_certificate_authority_data)
    token                  = data.aws_eks_cluster_auth.current.token
  }

I stumbled across one of his YouTube videos doing a DDD and EventStorming binge. I’d never heard of him prior. Definitely someone I watch for content from now.

Scott’s talks on DDD and functional programming are great. He also published an excellent book, “Domain Modeling Made Functional.”

https://fsharpforfunandprofit.com/books/

Original tweet is from March

> “petty drama” speaks volumes

Big time agree here. The comment was substantive and succinct. Saying it was “petty drama” in the top comment sets a tone for the convo.

That’s interesting because I had a credit card at 16 (it was on my parent’s account).

Not exactly sure. My current dentist said it’s rare for an autograft not to take, but it didn’t. He said my surgeon must have sucked.