For writing applications you only really need to know about the RPC APIs and how to use them. Contributing to the core servers (Bitcoin Core, btcd, lnd, cln, etc) is probably not the kind of work you want straight off.

I am working on Indranet https://github.com/Indra-Labs/indra and we are mainly going to be talking to lnd and neutrino/btcd through their RPC APIs, it helps sometimes to know how they work inside but, for most purposes aside from building these core systems, it's all about writing code that communicates to the APIs. You can mix and match, there is Bitcoin and Lightning APIs that are independent (mostly) from implementations, so the main thing is getting to know the version created for the language you intend to work with, and it is helpful if you look towards the actual service involved and ensure you know its specific differences from other implementations.

Read the books Mastering Bitcoin and Mastering Lightning Network. Build your own LN wallet in LDK as a learning experience. All this will set you on the right path. Godspeed!

I am building https://cyberhornet.network — A complete overhaul of the Bitcoin node running experience.

Over the last 16+ years that I've been a software engineer, I've based my career around a few simple principles:

• Always learn as much as you can: I spend most of my time learning. Comp Sci is a science that evolves continuously, if you're standing still you're moving backwards. Set aside allocated learning time and stick to it.
• Build and/or contribute: You already mentioned you'd made some contributions to open-source Bitcoin/Lightning services. This is awesome! Although job descriptions often have "3+ years of X" included in them, the team is trying to de-risk their inevitable hiring gamble. What they really want is someone who can build the things they want, you can demonstrate that without the years. (especially if you're sticking to that learning time).
• Understand the bigger objectives: This one might not be too relevant here, but it's important to understand your role as a software engineer in a business. Your job is to identify and resolve business problems to increase productivity and profitability— not to write code. Always try to keep in mind the bigger objectives and do your best to facilitate them, using code as a useful tool to help you do so.

In general, the Bitcoin space is full of potential improvements and the more great people we can encourage to contribute, the better chance we have of having a great impact on the world. The Bitcoin world needs you, as much as you need it!

Fuck books. Check out this repo. Or the stacker.news repo or any other repo that acts as a lvl 3 app and see if you can get to run or reproduce or extend it. There is going to be huge demand for this kind of stuff soon.

Read and study the book BITCOIN PROGRAMMING by Jimmy Song.

Go join wolfnyc talent pool. They're starting an incubator.

Сделай Bla Bla Car или Uber
Но используй двойной залог средств для подтверждения или отказа от поездки)))