It was exactly this kind of fun that led me to stay in my altcoin holdings and not participate at all in BCH. Liquidity puts a serious damper on a lot of slick crypto trade ideas - it's a "tortoise and the hare" kind of scenario.
We get to see those because they're advertising. That's the whole point of "you have to pay." When I read a hype story about a company someone else is paying.
Really good, cheap or free info about the present and future tends to lie not in a consumer paper but in dense, wordy PDFs that are cast offs of internal researchers at major multinationals and government bureaus. Those documents are often released to tell investors and taxpayers "here is how we view the situation and why" and their structural mission is to get the assessment right so that they make correct moves. There is little storytelling or human interest to these documents, but they are valuable for the same reason that knowing about the weather is valuable.
Business news sources tend to be clear headed, because they are in the space of news you can put a dollar value on, and hence will pay for to make more accurate. That doesn't make them perfect, since they still tend towards an editorial agenda favoring "business as usual" power centers over disruptive forces, but I don't feel like I'm being fed outrage most of the time.
I believe the right way to go is to focus on library code. If the long lived code is to prove exceptional it has to do so by being grabbed and bolted on to the new thing over and over, and that tends to favor an approach of libraries that assume very little, don't have many dependencies themselves, and opt for simple/robust API over being efficient. The API user can always recode the API for efficiency in their use case while as a library vendor your ability to guess at hotspots is limited at best, and as a consumer one is always looking for a library that can be used easily and disposed of quickly. In effect, "design by placeholder".
Simply: Stretch every day, morning and evening or even more often. Start with physical therapy type exercises and then gradually add stretches from ballet, gymnastics, wrestling, etc. It'll put a literal "spring" in your stride, improve posture and range of motion, and lower perceived pain both during exercise and at rest.
The weights also improve flexibility but not in as balanced a fashion. Stories abound of lifters with the posture of a gorilla.
This looks like an approach more akin to federation (or more accurately confederation) on social networks than the "distributed" notion of blockchain trust, which in practice, as noted, still exhibits centralizing political forces per chain, but is robust to most forms of direct attack. I do think that a mix of approaches is what will happen in the future since the two methods express different levels of trust and liquidity of transaction.
Pascal is a smaller language, and so easier to come to grips with at first glance. The syntax is tailored towards some verbosity which usually appeals to beginners. However, the downside is that you don't have a lot of leverage to do things in Pascal: Python pushes you down a path where you are writing something productive very quickly and can reach into the standard libraries to do many tasks - it makes some things very easy. Pascal requires some time to prepare the solution and encode it in syntax, and it's harder to find what you need, but there is usually code somewhere online that you can adapt. This is a lot to ask of beginners who want to do practical work, though. As of right now Pascal retains a lot of strength in desktop GUI code.
In terms of safety/dangerous code, modern Object Pascal style lets you be as dangerous as C if you want, but the default semantics are much more comfortable, and take you away from the danger zone more often.
Both Python and Pascal are relatively easy to get up and running with, and have pretty solid, standardized toolchains for industry use: in contrast C and C++ leave the build process relatively undefined and varying between compilers and platforms, which has resulted in a huge amount of friction to get any project building on a new machine.