David Bell

a mere operator

[David Bell @dastbe]

@jaredpalmer @github @georgebrock Will this also come with a fix for review comments getting lost in old revisions? Most people I know doing stacked diffs are editing commits in the stack rather than adding fixes on top.

[David Bell @dastbe]

@TobiM @0xdabbad00 imo iam data makes more sense from a “things i can operate” definition of service.

[David Bell @dastbe]

@TobiM @0xdabbad00 some services don’t have public endpoints, some endpoints service multiple services.

[David Bell @dastbe]

@mipsytipsy it’s also incredibly dumb (in a good way). text-based events that were batched and pushed to s3 on a minutely basis. this ends up being extremely cheap compared to other systems that lose a ton of precision.

[David Bell @dastbe]

@__steele what a shame, though it wasn’t clear what its market was. i wish the internal journaldb (originally named qldb) were made available instead.

[David Bell @dastbe]

@mikejulian any insights you can reveal on what’s keeping costs down?

[David Bell @dastbe]

@nathankpeck containers to genai pipeline is strong

[David Bell @dastbe]

@pinskinator immediately knew it was vancouver from the urban costco

[David Bell @dastbe]

@nathankpeck @thdxr biggest difference is that for cdk the cdk binary and cloudformation are the actual runtime, so in your “cdk deploy” step extending the runtime is extremely difficult compared to pulumi.

[David Bell @dastbe]

@nickcoult > If you need the data in the EBS volume to be retained after the task exits, check Delete on termination.

this statement sounds inverted?

[David Bell @dastbe]

@rchrdbyd @kohidave don't squat my prefixes, please and thank you

[David Bell @dastbe]

@Austen @pbreit @coffeelance the implication is that companies are using risk of long-term high inflation as a smoke screen to ramp prices way beyond cost increases from inflation. Now that inflation rate is going down, they have no excuse to keep these prices high.

[David Bell @dastbe]

@secengjeff @rakyll thats a mean thing to say about aurora limitless database (in preview)

[David Bell @dastbe]

@kohidave @AWSbrett does it understand dependencies between stacks, like outputs?

[David Bell @dastbe]

@nikovirtala @donkersgood @GergelyOrosz it’s called public cloud :).

[David Bell @dastbe]

@QuinnyPig if they put an apple and a zucchini in and put an arrow between them, it would actually be perfect

[David Bell @dastbe]

@BayesianNuance @amimevalepitito @notanastronomer i got a next day passport last week. you need to show that you have travel within a week. maybe spent 1 hour over the course of two days on it.

[David Bell @dastbe]

As an addendum, it's almost always better to use empty structs and fields rather than enums, since that empty struct can be easily extended with override configuration in the futre.

[David Bell @dastbe]

second: prefer a "topic-comment" style API with repetition than flat API where it's up to the service what fields can be configured together.

A good example is an API for defining http, tcp, or grpc ports

[Randall Hunt @ranman]

What are some random API design choices that you like?
What are some things people don't often think about when making APIs?

Yes, I am building an API. No, I can't be more specific at this time.

[David Bell @dastbe]

Instead, just create three structs for http, tcp, and grpc and put the configurable fields under each one

* end users know intuitively what fields they can set for a given protocol
* validation is just verifying only one protocol is specified, then validating that protocol