(1) Some haters of #Cardano are not only bag holders but also imperative developers.

If you are an imperative programmers you know that Plutus is not the most intuitive -> (https://t.co/m3fzq7rJYb)

It is, however, intuitive for people with IT financial background, e.g. banks

(2)

IELE + k framework will be a real game changer because there will be DSLs (Domain Specific Languages) in any programming language supported by K framework. The only issue is that we need to wait for all this
(3) Good news is that the moment we get IELE integrated into Cardano, we get some popular langs. To my knowledge we should get from day one: Solidity and Rust, maybe others as well?

List of langs: https://t.co/0uj1eBfrYj, some commits from many years ago..

@rv_inc ?

#Cardano
(a) Last but not least, marketing to people with Haskell, functional programming with experience and decision makers in banks is a tricky one, how do you market but not tell them you want to replace them. In the end one strategy is to pitch new markets, e.g. developing world
(b) As banks realize what is happening they maybe more inclined to join - not because they would like to but because they will have to - in such cases some development talent maybe re-routed to Plutus / Cardano / Algorand / Tezos
(c) It's a gamble because one doesn't know if and when this happens

Another approach is to market to developers with experience in Haskell and financial background via Catalyst, some banks may fire IT development staff on incoming recession so these people can play with Plutus
(d) If evaluation of banks continues to drop over time (some experts expect that) then they will be forced to reduce operational costs - in which case they will make IT people redundant including IT professionals (e.g. Haskell developers). Timeline is totally unclear here.
(e) More ambitious developers - even while working for banks can play around with Plutus or propose a project on ideascale - provided they are contractually allowed to.. Working in a bank is also very tiring, good money but working for IT staff over-hours is a norm.
(f) What is also critical in all this is that incentives need to be setup correctly. Cardano's treasury cannot support development indefinately. These projects need to find some way to at least support a small team of a domain expert, developer.
(g) Returns on business don't have to go in crazy amounts but enough to have some growth an support the cost. In many cases there could be developers from developing countries as often developers and domain expert from developed countries have very good salaries and jobs.
@threadreaderapp unroll

More from Tech

The 12 most important pieces of information and concepts I wish I knew about equity, as a software engineer.

A thread.

1. Equity is something Big Tech and high-growth companies award to software engineers at all levels. The more senior you are, the bigger the ratio can be:


2. Vesting, cliffs, refreshers, and sign-on clawbacks.

If you get awarded equity, you'll want to understand vesting and cliffs. A 1-year cliff is pretty common in most places that award equity.

Read more in this blog post I wrote:
https://t.co/WxQ9pQh2mY


3. Stock options / ESOPs.

The most common form of equity compensation at early-stage startups that are high-growth.

And there are *so* many pitfalls you'll want to be aware of. You need to do your research on this: I can't do justice in a tweet.

https://t.co/cudLn3ngqi


4. RSUs (Restricted Stock Units)

A common form of equity compensation for publicly traded companies and Big Tech. One of the easier types of equity to understand: https://t.co/a5xU1H9IHP

5. Double-trigger RSUs. Typically RSUs for pre-IPO companies. I got these at Uber.


6. ESPP: a (typically) amazing employee perk at publicly traded companies. There's always risk, but this plan can typically offer good upsides.

7. Phantom shares. An interesting setup similar to RSUs... but you don't own stocks. Not frequent, but e.g. Adyen goes with this plan.

You May Also Like