developer-roadmap VS substrate

Take off the gloves, get your hands dirty and do what you gotta do. You should be building stuff. Look at this site. Start from the top and work your way down for your chosen path.

As u/amablenderaa pointed out, taking a look at a roadmap like https://roadmap.sh which is split into different categories may be the best place to start.

link: https://roadmap.sh/

Small tasks and real goals help a lot. Check this out, https://roadmap.sh

Head over to https://roadmap.sh and checkout the frontend and backend tracks (maybe even devops if that's your thing). See if something catches your fancy and start working on it (along with DSA of course)

A community effort by the name of roadmap.sh has an exhaustive list of guides for multiple different paths into the software development world.

Should I spend my time learning more about Recursion, watch some condensed lectures on SICP 6.037 - Structure and Interpretation of Computer Programs (mit.edu) , go through this Developer Roadmaps?

Substrate developers should be aware of this change, making bounded storage the default for pallets. https://github.com/paritytech/substrate/pull/10662

As the rollout suggests, an important goal is making Polkadot as decentralized as possible. One suggested next step in this direction is to remove the Council as well as the Technical Committee as they’re both points of centralization, and a new governance model is being developed that does exactly that. In addition to that endeavour, the team at Parity is focusing on proposals for the next stages of the network and Robert Habermeier has talked about some upcoming efforts. These include async backing, a way to build and bundle validated parachain blocks before writing them to the Relay Chain, parathreads, and especially, a way to schedule parachain slot availability on a block-by-block basis. Some network optimizations have also been proposed, with a focus on improving collator and validator interactions.

You can follow the code updates in the Substrate repo, especially anything referring to BEEFY and MMR, e.g. the pallet here: https://github.com/paritytech/substrate/tree/ded44948e2d5a398abcb4e342b0513cb690961bb/frame/beefy-mmr

However, this exercise sets the stage for the topic, explaining some of the basics and showing them off in Rust, so that we can continue this journey by looking at how we would go about building a blockchain application that could actually be used in practice with a framework such as Substrate.

I'd love to see the M1Max times for https://github.com/paritytech/substrate

See https://github.com/paritytech/substrate/issues/9511 to keep track of progress on the issue, or read https://hackmd.io/wC6XTy36QsCmkfolX38Miw for a non-developer overview of the problem and what is being done to fix it.

The reason for limiting this is a temporary measure to ensure the stability of the network; too many nominators would make it possible for the Phragmén calculation for the validator election to cause nodes to OOM. I recommend reading https://hackmd.io/wC6XTy36QsCmkfolX38Miw to understand what the problem is, and https://github.com/paritytech/substrate/issues/9511 to follow along with what is being done to fix it (tl;dr is multi-block elections and long term a staking-specific parachain).

There are multiple development efforts to reduce (and hopefully essentially eliminate) the minimum nomination requirement. See this Github issue for details: https://github.com/paritytech/substrate/issues/9511

Keep in mind these measures are meant to be temporary, and the overall goal is the stability and security of the network. Multiple avenues of development are being done to mitigate this issue. For an overview of the issue, see https://github.com/paritytech/substrate/issues/9511