Hacker News new | past | comments | ask | show | jobs | submit login

This is a useful point of view I'll be adding to the toolbox. Looking at testing and type as TTP entities is already fun. This line:

> Making personal property functionality dependent on trusted third parties (i.e. trusted rather than forced by the protocol to keep to the agreement governing the security protocol and property) is in most cases quite unacceptable.

sums up a line of thinking I'd like to explore a bit.

> These institutions have a particular way of doing business that is highly evolved and specialized. They usually cannot "hill climb" to a substantially different way of doing business. Substantial innovations in new areas, e.g. e-commerce and digital security, must come from elsewhere.

Work I've done in finance-related shops fits neatly into the TTP model, and that model explains most of what I used to see as tech debt. As a TTP being able to guarantee a result was a core part of our business, so processes would be set in stone once people used them to do serious work. If the initial design was written and implemented by people with a grasp on each domain it touched, you'd need to have that all under your belt before thinking about real changes.

The immutability + cost factor makes existing work look foundational and innovations in processing metabolite are easy to spec out and calculate return value on.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: