Léo Vincent

software engineer currently working on blockchains systems :)

[Léo Vincent @leoovct]

what it feels like to work in web3...
but that's cool though 🤪

[Pratik Patil @pratikspatil024]

ICYMI, VEBloP is now live on Polygon testnet.

[Polygon | POL @0xPolygon]

https://t.co/was07xZKkF

[Katana ⚔️ @katana]

wake the fk up samurai. this is katana.

not just another general purpose chain. a defi chain forged to kill idle assets via deep liquidity & high yield. public mainnet coming late june.

incubated by @0xpolygon x @gsr_io

pre-deposits live ⚔️ stop sleeping on your bags

[Mudit Gupta @Mudit__Gupta]

Polygon will 10x its throughput and TPS within the next few weeks.

Read the proposal for veBloP (name TBD) and give your feedback.

https://t.co/YbkgYvhXps

This is just the start, expect lots more as we head towards Polygon chain's 5 year anniversary.

[Léo Vincent @leoovct]

@evan_van_ness @WeekInEthNews thank you for all the hard work, WiE will be missed!

[Léo Vincent @leoovct]

+1 💚

[Georgios Konstantopoulos @gakonst]

my biggest shoutout of 2024 is going to @KurtosisTech -- just game changing tool for testing Ethereum infrastructure, cannot live without it

[riptide (sf) @0xriptide]

readable solidity is being replaced with highly commented yul

at some point you might as well not bother even verifying the contracts

i know the rationale behind it but this is retarded

[Jarrod Watts @jarrodwatts]

Developer experience (DX) is the single most important thing all developer tools (especially blockchains) should be optimizing for.

A blockchain's target audience is developers.

If your DX is bad, every other team suffers.

If your DX is good, every other team benefits.

Let's look at one example... Marketing:

How much are you spending to acquire developers into your ecosystem, per developer?

Consider your marketing, socials, events teams, etc...

Is it 4 figures? 5? 6? ... 7 figures per developer?

That might sound ridiculous, but 7 figures is not out of the realm of possibility for blockchains.

Keep in mind, According to the Electric Capital report, every chain (including all L2s & Solana) other than Ethereum has less than 1,000 full-time developers.

The point is, you are currently spending a lot to get one developer to even try building on your chain.

Ultimately, the goal of your marketing (and many other teams) is to get more people to build on your chain.

The bottom of the funnel or "conversion" for these teams' effort is getting a developer to try to build something on your product.

That conversion is the starting point of your DX.

The conversion is the developer going to your docs and trying to build something.

It begins a new funnel where the developer tries your product, is successful, continues being successful, and after being successful; advocates for your product.

If your bullshitted, oversold, and your DX under-delivers... you just lost that developer.

They can't even get a hello world working? What kind of nightmares are further down the track for them?

Unless they *have to* use you (i.e. you paid them a lot to do so, or their boss made a business deal out of their control, etc.)... they give up. Quickly and angrily.

So, you lost one developer...

No worries, just 4,5,6, or 7 figs right...?

But how many developers has this happened to? 1? 10? 100? 1000? 10,000?

How much do you have to compensate because of this? Are you paying teams 7/8 figures to build on you?

How much harder is this making your marketing efforts? What about your BD efforts?

Is it frustrating for your employees to have that reflect on their reputation? Are they leaving because of it?

It affects every part of your business.

Immediately there is an argument that you should pay someone, 5,6,7 figures to own your DX and stop the bleeding... but, this isn't even the worst part.

Above all, devs trust other devs. The best form of marketing for your product is word of mouth from other developers; peers they trust or sometimes respected engineers online.

That dev you just lost due to poor DX is going to tell their peers, "Yeah, that shit sucks... don't use it".

They might even take it to the next level and loudly shit on your product to all their followers.

You've now lost (or at least, began a very difficult uphill battle) 10, 100, 1000... developers from your bad DX. Maybe you lost staff (quietly or not).

The direction of developers flowing into your developer experience from different efforts is massive.

The opposite direction is also true. With good DX, developers will create value for you that is impossible to generate internally.

Hearing that your DX is good from someone a developer respects (usually another, "better" developer) is worth more than anything you can produce yourself.

For example, any marketing you do going forward is perceived in the context of the DX that your audience had.

Your marketing can become organic and driven by your community of developers talking positively about you.

This two-way relationship is true for basically every other team in your business too.

BD/ecosystem:
- Teams you work with have their developers work with your tools. Despite being forced to use you now, they remember your DX moving forward in future projects. If it sucked to use your product, they will avoid you.

- Your DX can make/break the decisions of teams going into the deals. If the devs of the team are shouting "please god no" to your business team, it's a much tougher battle to win.

Sol eng/community/support:
- Bad DX? Your dev rel / engineers will spend more time supporting individuals than creating scalable resources to power good DX.

- How much stress your support teams are under is largely determined by how good/bad your DX is. Developers need support when things are not obvious.

On top of this, other teams building on your chain/product are ultimately restricted by how good your DX is. The quality of products created is heavily impacted by what your developer experience enables.

Good DX -> Good products -> Good UX.

Optimize for developer experience.

[Léo Vincent @leoovct]

@fede_intern lambdaclass never disappoints

[tincho 🪷 @tinchoabbate]

Dear players of Damn Vulnerable DeFi, rumours are true.

The most vulnerable smart contracts in all web3 have been upgraded. V4 is out! 🔥

This is a major update to the game, packed with new challenges and improvements all around.

https://t.co/i1ePdfnpHN

[Léo Vincent @leoovct]

@makemake_kbo Fridays are for drinking beers, not breaking production 🤪

[Léo Vincent @leoovct]

@reduzio @Blender @godotengine

[Léo Vincent @leoovct]

LFG!!! Let's play!! :)

[tincho 🪷 @tinchoabbate]

Dear players of Damn Vulnerable DeFi, rumours are true.

The most vulnerable smart contracts in all web3 have been upgraded. V4 is out! 🔥

This is a major update to the game, packed with new challenges and improvements all around.

https://t.co/i1ePdfnpHN

[Léo Vincent @leoovct]

@phklive @0xPolygonMiden @phil_h @MangroveDAO always grinding 🔥🔥

[Léo Vincent @leoovct]

@PatrickAlphaC

[John Hilliard @praetorian]

Very cool to see how advanced the local ethereum testing has gotten with @KurtosisTech - I'm excited to try out assertoor. Awesome stuff from @parithosh_j

[Léo Vincent @leoovct]

@phklive @0xPolygonMiden propre la veste 👀

[Programmer Humor @PR0GRAMMERHUM0R]

pleaseStop https://t.co/kRYfibuVUa

[Polygon | POL @0xPolygon]

pack your things, we’re heading to brussels 🧳

explore the thread to get the lowdown on our @ethcc talks, killer side events and late night soirees ↯

[Kurtosis @KurtosisTech]

We're excited to announce that Kurtosis is now fully open-source under the Apache 2.0 license! 🦢✨

(1/4)