1. Rewrite everything in Go or Rust for the sake of it.
2. Pretend AWS and DNS do not exist and that the web is decentralized.
3. Read blockchain. Lots of it. Write about it more than you read about it.
4. Success. Let the big bucks rain on you.<p>But seriously, are you considering getting into this just for the bucks? I'd suggest you check out what Moxie and other respectable folks have to say about this first, e.g:<p><a href="https://moxie.org/2022/01/07/web3-first-impressions.html" rel="nofollow">https://moxie.org/2022/01/07/web3-first-impressions.html</a><p>You can read about many more fiascos online. I think there are a million more interesting things to get into. The nice thing about recessions is that it cuts out much of the BS, and we've already seen quite a few of these startups go down for good.
In the true spirit of Web3 you can simply do the Ethereum tutorial, "read" some whitepapers (they aren't meant to be though about deeply anyway) and start adverstising yourself as a blockchain expert.<p>Don't overthink it, the people you'll work with are already grifters themselves.
Determine what part of the stack you want to be on<p>Most projects are smart contracts, so thats Solidity and browser frontends like React<p>whereas in the Solana ecosystem both the node software and the smart contracts are written in Rust<p>amongst smart contracts there are about a dozen sectors:<p>Lending<p>Staking<p>Insurance<p>Options<p>Futures<p>AMMs<p>Optimizers<p>All the way over to NFTs<p>Within NFTs there are about 5 distinct sectors too, with the most action and capital occurring in the NFT <i>collections</i> space, followed by NFT marketplaces<p>and then after all that there are Web 2.0 style SaaS companies that provide services to web 3 customers for subscription fees. thats probably the most boring because they cant juice your compensation with tokens <i>or</i> publicly traded shares.<p>so pick your sector first.
I started my path as BE 5 years ago and now I run a blockchain company.<p>My strategy was:
1 - learn just the basics on each vertical (bitcoin, EVM, smart contracts, consensus protocols, game theory) - it wasn't difficult having a background as engineer
2 - get a job as PM/PO to be in touch with as many projects as I can
3 - get a deep understanding of the market needs
4 - start working as low level developer on a particular (selected) project, to understand the core and become an expert
5 - manage my own team to sell services (outsourcing) to other entrepreneurs
6 - scale num.5<p>I share with you a doc I wrote a time ago, describing the roadmap I propose to learn the basics: <a href="https://medium.com/rather-labs/the-roadmap-to-become-a-blockchain-gladiator-f9ce369f0d94" rel="nofollow">https://medium.com/rather-labs/the-roadmap-to-become-a-block...</a><p>Also, if you want to check my company, you can do it at ratherlabs.com<p>I wish you the best on this exciting path!
Stuff you learn in "web2" translates to web3, but the opposite is not true: the tolerance for risk and failure in the crypto space is just so much higher than anywhere else, that engineers who learn in that environment never really have a chance to develop the baseline technical skill expected by any other part of industry.<p>It's really a tragedy that the pump-and-dump web3 space is siphoning off so many entry-level programmers. When the music stops, it's going to be a lot of work for those people to transition elsewhere.
This is a fairly jaded take, but my impression is that "blockchain engineers" often expect to be able to work pseudonymously, which implies that credentials and reputation are not as important as in other business domains. One consequence of this is that it's probably easier to break into the field if you perform well in an interview; another consequence is rampant insider fraud.
> <i>Avg. BE makes about $160k, is it worth to get into web3 now</i><p>That number is probably old, before the crypto bloodbath of the last few months.
1. Pour the Kool-Aid into a large pitcher. The pitcher needs to be big enough to hold at least a gallon of water. Pick the biggest one you have so there's plenty of room to stir your Kool-Aid mixture without splashing liquid everywhere.<p>2. Add the sugar. Use a measuring cup to measure out a cup and a half of sugar, then add it to the pitcher.<p>3. Add the water. Pour in an entire gallon of water (that's 16 cups) on top of the Kool-Aid mix and sugar.<p>4. Stir the ingredients well. Keep stirring for about three minutes, until the sugar completely dissolves. If you drink it too fast, the sugar will still be in its crystal form.<p>5. Taste test your Kool-Aid. See if it needs more sugar or water. Everyone likes their Kool-Aid to taste a little different.<p>6. Enjoy over ice. Kool-Aid is delicious poured over ice. Fill up a glass with ice and pour in the Kool-Aid. Store your leftover Kool-Aid in the refrigerator for later use.<p><a href="https://www.wikihow.com/Make-Kool-Aid#Classic-Kool-Aid_2" rel="nofollow">https://www.wikihow.com/Make-Kool-Aid#Classic-Kool-Aid_2</a>