601 karma · joined February 10, 2022
Citation needed.
Btw, calling Tornado Cash a "DPRK tool" is disingenuous. It's a privacy tool.
Therein lies the rub.
I think amateur "trading" attracts a specific brand of idiot that is high/left on the Dunning Kruger curve. While taking money from idiots is a viable (even admirable) business strategy, you may want to fully automate customer service to retain your sanity.
It's much better to pass and forget.
Something that impedes my ability to pass unsafe drivers is unsafe.
I have not found this to be true at all. I frequently have very long (300+ line) pure functions that do one thing, and the tests are designed to be oblivious to whatever intermediate representations are used. In fact, I think it's an anti-pattern to pull types out just for testing: tests should not be so granular that they affect how you design functions.
For example, a function that takes a JSON string containing multiple objects and returns an SQL string for a batched INSERT operation. I can easily achieve 100% coverage with a table-driven test just checking inputs and outputs.
I frequently use function-local types and function-local functions that are reused within the function. Testing has never been a problem.
> Second, as the code grows, you want to be able to refactor things freely, and types embedded in functions form a barrier to refactoring because to refactor you'll have to do something to expose that type now to multiple functions.
This hasn't been my experience either. When refactoring, I'm usually doing more encapsulation, not less. On a first pass, I write everything to have access to everything else. Only after I have a clearer idea of boundaries do I refactor.
[1]: https://justine.lol/
My experience as well. This is why Taleb's writing appeals to me most for "business advice": structure everything to benefit from chaos, and build an environment conducive to tinkering and breakthroughs. Highly recommend his article, "Understanding is a Poor Substitute for Convexity"[1].
[1]: https://www.edge.org/conversation/nassim_nicholas_taleb-unde...
You can certainly use the database as a "dumb storage" tool in the hexagonal architecture, that is, as just another adapter. But most of the time you'll end up re-creating RDMS features in poorly written/documented application code that has to interact with the database anyways. Why not just do it all in the database? With a RDMS core, hexagonal adapters can be pure functional components, making them much easier to reason about and maintain.
For more on this idea, and how to avoid pitfalls with the hexagonal pattern, I recommend reading Out of the Tar Pit [1]. It's a short but highly influential paper on "functional relational programming".
I did and it was incredibly alienating. I will make sure my kids don't have to go through that.
Officially.