Mastodawn

Hynek Schlawack Aug 4, 2023

tfw you’ve created something that excites you like nothing in years but it feels like you have to write a book first to lay the context to make wide appreciation even possible

Show thread

Chris is.Aug 5, 2023

@hynek I was wondering if you'd be solving the worst part, but I think "The main downside is that it's impossible to verify whether all required dependencies have been configured without running the code." answers my question there.

That's always the tough thing; how to be sure your various environments provide the same necessary set of capabilities when not every code path is going to reach those service discovery steps. Even 100% test coverage doesn't save you :(

Show thread

Hynek Schlawack Aug 5, 2023

@offby1 I find it very easy to test if you make sure that every resource is set in the same place depending on some flag/setting. Also there’s Sentry/monitoring I find people are making a big deal out of nothing but maybe my arch style is just very different. You can just as well misconfigure something I don’t feel this is adding a new error category.

Show thread

Chris is.

@hynek I don't think it's adding a new one, per se, but — depending on how you started -- it might be pushing the errors into surprising places in your call flow instead of having them happen up front. There is something to be said for having an expensive startup that binds ALL THE THINGS right then, so that you never get to wonder when one of your users will call something that fails to init much later, or conditionally depending on the availability of external systems.