Post #2232192

@tomw@mastodon.social @silasmariner@hostux.social I guess I should have clarified "mess" better. If I make, say, an invoice parsing tool, as an HTTP service that stores events and sends emails, then "everything about invoicing and it's parsing", all its messy and real world constraints are put front and center. But HTTP, emailing, persistence? Way messier, but utterly uninteresting to the domain of invoices or the domain of parsing. Boring details. So those are put out of sight. Abstracted away.