telecomsteve

Lesson learned: start with fewer metrics and observe how they are used and interpreted. It is much easier to expand correctly from there. Collecting requirements in a single pass and building a monolith is rarely as productive as it seems - because the barrier to adding things and shifting responsibility to the dashboard is so low in the beginning, that it can easily become a dumping ground.

AFAIK this would be the first such firm focusing on zero knowledge cryptography. The blog doesn't say they are focusing solely on blockchain, but there is a noticeable gap there, as such financial contracts move increasingly to zero-knowledge implementations.

A web3 stack, everything client-side and peer-to-peer. HTML/CSS/JS for front-end. JS/blockchain for backend. JS client-side storage/compute, JS libp2p library for peer-to-peer discovery, networking, syncing, updates, user-generated content, etc. Blockchain for things that need to be tamper-proof or involve payment.

In theory I agree with the OP, but I am having the reverse problem now. My startup has an equal pay policy. I live in San Francisco and have a San Francisco salary, but cannot afford a home here without saving for many years and having a very lean budget.

Next to me are colleagues who live in countries where the cost of living is a fraction. They tell stories of the first and second homes they are building and how they agree with the pay policy. They are living a quality of life that is beyond anything I can have while living in San Francisco, and I partly resent this.

Within the company, people have and are still moving to low cost areas, because the company is fully remote. I however am married and my partner cannot as easily be relocated.

I don't give my company name here because it is very small with only a fraction or employees living in San Francisco.

Greetings everyone, this is my first post to HN (long-time lurker). I'm finishing a PhD and created this website template to show both research and programming work. The site is made as flat files (with no scripting) to be served ideally from object storage like S3. I thought others may find it useful, so I've placed it on GitHub. Contributions, feature requests or general feedback are much welcomed.