Weekly update on development process (Jan 3, 2022)

Weekly progress

  1. 👬 Designed a marketing-based motivation system for team members. The basic idea is to pay for marketing messages, not for code. So expect more social media activity from us ;) Of course, the messages must be valuable for users: they must describe new features or explain how to use existing features.
  2. ⚒ Improved the setClaimsTask to handle smart contract balances (work-in-progress).
  3. ⚒ Improved the landing page on dev host (work-in-progress).
  4. 🔄 Migrated from LastPass to 1Password due to multiple reports of compromised master passwords. Please note: as of Jan 3, 2022, there is no indication that any of our properties were accessed by attackers. However, we decided to migrate anyway to minimize the risk.

Lessons learnt

  1. The salary system is broken: it pays people for their time, not for their work. It underpays the most productive employees & overpays the least productive employees. The productive employees can renegotiate salaries based on their performance, but in practice they rarely do — the productive employees would rather do the actual work than negotiate stuff.
  2. The problem would be solved if we had an objective metric of a programmer’s productivity. However, a lot of people have tried to find it before, and they haven’t, so we should not spend our time on that. Instead, we have to look for alternative pay negotiation systems.
  3. One such system is found on freelance marketplaces. It’s a bid-auction system where a client posts a job, and the freelancers post their bids (how much they want to get paid for this job).
  4. This system moves the risk from the client to the freelancer. However, this has an effect of filtering out the best freelancers, because they don’t want to bear the risk, and they are so obviously good that clients are willing to give them salaries instead of fixed payments.
  5. We need to hit a sweet spot: hire the employees who are not-so-obviously-good (otherwise the big companies with bigger budgets would propose a bigger salary / larger total compensation), but who are good enough for our tasks.

Next week’s focus

  1. ⚒ Finish the landing page.
  2. ⚒ Continue writing the script for migrating the balances & liquidity from ETH to BSC (SHLD to COLI).

About Shield Finance

--

--

--

With Coliquidity, you can provide liquidity using only 1 token. We match two providers to create a joint position. Less risk, more reward for each LP 😉

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Hacker101: Postbook

We keep your data safe!

How to subscribe to security notifications from Forta?

8 Simple Steps to Take When Your Credit Card is Stolen

{UPDATE} Word cookies Hack Free Resources Generator

Early Detection of Exchange Zero Day? Hindsight Indicators

NULS Security Upgrade Alert

Medical Provider — Reflected XSS in Search Results

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Coliquidity

Coliquidity

With Coliquidity, you can provide liquidity using only 1 token. We match two providers to create a joint position. Less risk, more reward for each LP 😉

More from Medium

Weekly update on development process (Mar 7, 2022)

Arc Finance: Mechanisms and the AUM Tools

Get Started — Z3NS

CashCow Protocol Weekly Report 📣