5,681 karma · joined July 10, 2013
The team worked with researcher Daniel Riday who reproduces ancient tattoo designs on his body using historical methods.
Now that's dedication to research!
[0] https://www.fenwick.media/all-blog-posts/mastery/broetry-dea...
The beginning of this video has some of that: https://youtu.be/Nrb3LN7X1Pg
In my current job as a technical due diligence advisor, I frequently recommend multi-AZ setup but specifically not multi-region, because the former is easy and worthwhile while the latter carries a lot more operational overhead (you become much more sensitive to various latencies and network jitters) and you now need to think about things like synchronous vs async replication, etc. Much better to focus dev effort on the product, rather than eke out an additional .001% of availability (unless availability is a super critical component).
My initial concerns would be:
- Maintainability: the "duct-tape logic", as you put it, sounds like spaghetti code from hell. Making sense of a feature comprised of tons of chained third party calls will be a nightmare.
- Expressiveness: complex functionality may require complex code. I don't quite understand how you would write even medium complexity algorithms using this system.
- Reliability and performance: you are now entirely at the mercy of third party providers. This is often the case with SaaS products, but this seems like a particularly severe case. Each hop reduces performance as well, which may impact user experience (assuming we're talking about user-facing features).
- Quality: by moving business logic out of code, you're throwing out testability, so no more unit tests. I guess integration tests could still happen, but they're going to be slow, expensive, and involve someone writing the actual code - which, given the premise of product managers creating features, seems very unlikely.
No issues with memorization, however. Brains are weird.
INSUFFICIENT DATA FOR MEANINGFUL ANSWER
Source: The Last Question by Isaac Asimov (https://users.ece.cmu.edu/~gamvrosi/thelastq.html)